<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
0D54z00009Wmq14CABOkta Classic EngineIntegrationsAnswered2023-08-14T15:36:58.000Z2023-08-12T08:49:40.000Z2023-08-14T15:36:58.000Z
RajeshT.69629 likes this.
  • Hi @RajeshT.69629 (Customer)​ , Thank you for reaching out to the Okta Community!

     

    Current features allow for both implementations where Okta could be the Identity Provider for OIDC apps and/or implementations where OIDC apps might be the Identity Provider for Okta. This not to be interpreted as both at the same time for the same app. A valid use case could be for example: You can have Okta be the IDP for OIDC_APP_1 and OIDC_APP_2 could be the IDP for Okta. 

     

    Please review the following documentation and their respective related articles for the different use cases:  

     

    Okta as IDP.

    OIDC app as IDP for Okta. 

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

    --------------------------------

    Okta Identity Engine (OIE) Ask Me Anything: Get answers from product experts by clicking here.

    Expand Post
This question is closed.
Loading
OIDC Okta as IdP and SP