<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z0000A4oZq9CQEOkta Classic EngineAdministrationAnswered2024-05-08T16:44:52.000Z2024-05-07T18:54:05.000Z2024-05-08T16:44:52.000Z

MatthewH.10249 (State of Iowa) asked a question.

What are the downsides to changing all custom Authorization Servers to "DYNAMIC" issuer mode?

What are the downsides to changing all custom Authorization Servers to "DYNAMIC" issuer mode? We have some custom Authorization Servers that predate the "DYNAMIC" issuer mode option so they are assigned currently to either to "Custom URL" or "Okta URL". For consistency I was thinking about changing them all to "DYNAMIC" but don't want to introduce any issues for apps using them. Would this be transparent to apps since "DYNAMIC" would allow either URL?

 

The following Okta documentation references the "DYNAMIC" issuer mode that I'm referring to above.

https://developer.okta.com/docs/reference/api/authorization-servers/*property-details

"After you configure a custom URL domain, all new Custom Authorization Servers use CUSTOM_URL by default. If the Dynamic Issuer Mode feature is enabled, then all new Custom Authorization Servers use DYNAMIC by default. All existing Custom Authorization Servers continue to use the original value until changed using the Admin Console or the API, so that existing integrations with the client and resource server continue to work after the feature is enabled."


This question is closed.
Loading
What are the downsides to changing all custom Authorization Servers to "DYNAMIC" issuer mode?