You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
the OKTA property okta.oauth2.redirect-uri is automatically prefixed with {baseUrl} computed from current request values.
This does not work when OKTA application is deployed behind some proxy with different url.
The only way how to overcome this problem and set full url (like https://proxy.com/{action}/oauth2/code/{registrationId}) is to set directly spring.security.oauth2.client.registration.okta.redirect-uri and avoid using okta.oauth2.redirect-uri as X-* headers are not allowed to use in my case.
I would suggest to remove {baseUrl} from this line in OktaOAuth2PropertiesMappingEnvironmentPostProcessor.java and let the developer decide whether the uri should be automatically computed or not:
Hi,
the OKTA property okta.oauth2.redirect-uri is automatically prefixed with {baseUrl} computed from current request values.
This does not work when OKTA application is deployed behind some proxy with different url.
The only way how to overcome this problem and set full url (like https://proxy.com/{action}/oauth2/code/{registrationId}) is to set directly spring.security.oauth2.client.registration.okta.redirect-uri and avoid using okta.oauth2.redirect-uri as X-* headers are not allowed to use in my case.
I would suggest to remove {baseUrl} from this line in OktaOAuth2PropertiesMappingEnvironmentPostProcessor.java and let the developer decide whether the uri should be automatically computed or not:
properties.put("spring.security.oauth2.client.registration.okta.redirect-uri", "{baseUrl}${okta.oauth2.redirect-uri}");
Or is there any reason why baseUrl must be always computed?
Thanks a lot,
Jiri
The text was updated successfully, but these errors were encountered: