Skip to content

Conversation

@inc-osaulenko
Copy link

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
Contributor

Thank you for the submission!

Internal Ref: OKTA-805980

@tony-ic
Copy link

tony-ic commented Feb 3, 2025

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

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