Skip to content

Detect origin for urls of different forms#1538

Open
inc-osaulenko wants to merge 1 commit into
okta:masterfrom
inc-osaulenko:fb_detect-issuer-origin
Open

Detect origin for urls of different forms#1538
inc-osaulenko wants to merge 1 commit into
okta:masterfrom
inc-osaulenko:fb_detect-issuer-origin

Conversation

@inc-osaulenko

Copy link
Copy Markdown

Currently, origin is detected by taking the part of URL prior to /oauth2/ and for URLs like this

https://www.domain.com/oauth2/{some-client-id}

It works as expected. However, when the service that uses OKTA API is behind a multi-tenant proxy and URL will be like

https://www.domain.com/{lang}/{tenant-id}/oauth2/{some-client-id}

It doesn't work. There is an option to do the same thing using (new URL('...')).origin but that will require to add another polyfill for IE11. This one uses Array.prototype.split which is available in IE11 and requires no polyfill.

@jaredperreault-okta

Copy link
Copy Markdown
Contributor

Thank you for the submission!

Internal Ref: OKTA-805980

@tony-ic

tony-ic commented Feb 3, 2025

Copy link
Copy Markdown

Hello! Any updates on this? When it can be merged?

@tony-ic

tony-ic commented Jun 4, 2026

Copy link
Copy Markdown

Hi team,

It’s been nearly two years since this feature request was accepted for review, but there haven’t been any updates. Can you please provide an update on its status and whether it is still being considered for implementation?

This functionality is important for our mutual customers, and the lack of visibility makes planning difficult.

Any guidance would be appreciated.

@jaredperreault-okta

Copy link
Copy Markdown
Contributor

We will need a signed CLA by the author in order to merge this.

This PR also needs tests before it can be accepted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants