<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
0D5KZ00000eFV200AGOkta Classic EngineSingle Sign-OnAnswered2025-04-30T17:46:57.000Z2025-04-07T22:53:18.000Z2025-04-30T17:46:57.000Z

RayA.78577 (OpenSesame) asked a question.

IdP Routing patterns for complex organizations with multiple IdPs

We're looking at how we can solve the problem of customers having multiple IdPs and needing to route users to the right IdP. Does anyone have best practices for this use case for both OIDC and SAML IdPs?


  • Paul S. (Okta, Inc.)

    Hello @RayA.78577 (OpenSesame)​ Thank you for posting on our Community page!

     

    If your company has multiple IDPs, we would recommend to have a unique attribute for each company user and use that for the routing rule.

    Let's say you have Customer A, B and C, all users for these 3 companies will have a CompanyID attribute but each with his own unique value.

    Company A's users will have attribute CompanyID set to "value1", company B's users with have attribute CompanyID set to "value2" and Company C's users with have attribute CompanyID set to "value3".

    When setting up the routing rule, you will select User match against attribute, and select the attribute as CompanyID with the value to the respective customer. Please also see screenshot attached as an example:

     

    image.pngThank you for reaching out to our Community and have a great day!

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge

    Expand Post
    Selected as Best
  • Paul S. (Okta, Inc.)

    Hello @RayA.78577 (OpenSesame)​ Thank you for posting on our Community page!

     

    If your company has multiple IDPs, we would recommend to have a unique attribute for each company user and use that for the routing rule.

    Let's say you have Customer A, B and C, all users for these 3 companies will have a CompanyID attribute but each with his own unique value.

    Company A's users will have attribute CompanyID set to "value1", company B's users with have attribute CompanyID set to "value2" and Company C's users with have attribute CompanyID set to "value3".

    When setting up the routing rule, you will select User match against attribute, and select the attribute as CompanyID with the value to the respective customer. Please also see screenshot attached as an example:

     

    image.pngThank you for reaching out to our Community and have a great day!

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge

    Expand Post
    Selected as Best
This question is closed.
Loading
IdP Routing patterns for complex organizations with multiple IdPs