<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
0D54z00006yR2zcCACOkta Classic EngineIntegrationsAnswered2024-03-25T14:45:11.000Z2021-05-19T06:53:19.000Z2021-05-22T14:18:57.000Z

blu4l (blu4l) asked a question.

Open ID well known configuration URI

Hi,

I work for a SaaS company which supports Okta as an identity provider.

 

Our platform uses Open ID Connect, and when setting up an identity provider requires a well known metadata URI.

 

Today we found that one of our customers had a metadata URI in the form https://CUSTOMER_NAME_HERE.oktapreview.com/.well-known/openid-configuration. This is a bit different to the form we've seen before which was https://CUSTOMER_NAME_HERE.okta.com/.well-known/openid-configuration.

 

Can anyone explain the significance of the oktapreview.com domain versus the okta.com domain? What causes some accounts to use one or the other?

 


  • User15871004093001868702 (Vendor Management)

    Hi Tom,

     

    This is Florin from Okta Support. All tenants with oktapreview.com are sandbox environments where customers can test out some new features or products free of charge depending of the type of feature, so they can later implement some changes into their production tenants which are the okta.com tenants. So long story short the URI is the same but it depends of the type of tenant that you have. If a customer has sandbox environment it will be domain.oktapreview.com and if the customer has production environment it will be domain.okta.com.

    Hope this answers your question.

    Have a great day ahead!

    Expand Post
This question is closed.
Loading
Open ID well known configuration URI