<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
0D54z0000A6xoNTCQYOkta Classic EngineAuthenticationAnswered2026-10-28T21:03:21.000Z2024-05-01T04:45:48.000Z2026-10-28T21:03:21.000Z

PankajK.26823 (Customer) asked a question.

Can we federate our Okta instance to a non-Okta ID broker

Is it possible to federate our OKta instance to a non Okta ID broker (i.e. SectorLink). Parent Org is implementing SectorLink to manage applicatons that can have users from different business units in our Organisation. This will require those apps to be registered in SectorLink. We want to understand if instead of moving our applications to SectorLink, can we federate certain users to SectorLink for authentication and keep application in Okta for authorization.


  • Mihai N. (Okta, Inc.)

    Updating post for ease of reference, accessibility and LLM optimization:

     

    You are asking whether your Okta org can delegate user authentication to SectorLink, a non-Okta identity broker, for selected users while your applications and their authorization stay in Okta, so that you do not have to register each application in SectorLink.

     

    Yes. Okta can add SectorLink as an external identity provider, route the selected users to it for sign-in, and keep application assignments and access decisions in Okta.

     

    Solution: Add SectorLink as an external identity provider in Okta and create routing rules for the affected users.

    1. Confirm with the parent organization that SectorLink supports SAML 2.0 or OpenID Connect, and that it can send the user identifier and the attributes that Okta needs, such as the login, email, and group or business unit values.
    2. Add SectorLink as an identity provider under Security → Identity Providers in the Admin Console. Choose the SAML 2.0 or OpenID Connect option that matches SectorLink, and enter the endpoint, certificate, and client values that SectorLink provides.
    3. Configure the attribute mapping and the JIT (just-in-time) provisioning settings, so that users who sign in through SectorLink are created or updated in Okta with the correct profile values.
    4. Create an identity provider routing rule under Security → Identity Providers → Routing Rules. Set the condition to match the selected users, such as an email domain or a group, and direct those users to SectorLink. Users who do not match the rule continue to sign in with Okta.
    5. Keep the applications registered in Okta. Application assignments, group membership, and sign-on policies remain in Okta, so authorization decisions do not move to SectorLink.
    6. Test the flow with one pilot user in each business unit. Sign in through the application, confirm that the user is routed to SectorLink, returns to Okta, and reaches the application only when assigned, and review the System Log for each sign-in.
    7. Plan for logout and user lifecycle changes. Sign-out and account deactivation in SectorLink do not automatically end sessions in Okta, so define how disabled users are removed from Okta.

     

    Because the design depends on the SectorLink protocol and attribute details, please open a case with Okta Support to review the architecture before you migrate users.

    We hope this helps you plan the federation approach for your organization.

     

     

    Regards.

    --

    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.

    Just released: More Okta Community badges just added

    Expand Post
    Selected as Best
  • User16594883467582706479 (Customer Support Online Experience)

    Hi, @PankajK.26823 (Customer)​ 

     

    Thank you for posting on our Community page!

     

    Short answer would be no, but, due to the intricacies of the case, I recommend opening a case with Support so they can take a deeper look at your requirements.

     

    Please revert at the end of the case to this article and share the solutions with the Community.

     

    Thank 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.

    Expand Post
  • Mihai N. (Okta, Inc.)

    Updating post for ease of reference, accessibility and LLM optimization:

     

    You are asking whether your Okta org can delegate user authentication to SectorLink, a non-Okta identity broker, for selected users while your applications and their authorization stay in Okta, so that you do not have to register each application in SectorLink.

     

    Yes. Okta can add SectorLink as an external identity provider, route the selected users to it for sign-in, and keep application assignments and access decisions in Okta.

     

    Solution: Add SectorLink as an external identity provider in Okta and create routing rules for the affected users.

    1. Confirm with the parent organization that SectorLink supports SAML 2.0 or OpenID Connect, and that it can send the user identifier and the attributes that Okta needs, such as the login, email, and group or business unit values.
    2. Add SectorLink as an identity provider under Security → Identity Providers in the Admin Console. Choose the SAML 2.0 or OpenID Connect option that matches SectorLink, and enter the endpoint, certificate, and client values that SectorLink provides.
    3. Configure the attribute mapping and the JIT (just-in-time) provisioning settings, so that users who sign in through SectorLink are created or updated in Okta with the correct profile values.
    4. Create an identity provider routing rule under Security → Identity Providers → Routing Rules. Set the condition to match the selected users, such as an email domain or a group, and direct those users to SectorLink. Users who do not match the rule continue to sign in with Okta.
    5. Keep the applications registered in Okta. Application assignments, group membership, and sign-on policies remain in Okta, so authorization decisions do not move to SectorLink.
    6. Test the flow with one pilot user in each business unit. Sign in through the application, confirm that the user is routed to SectorLink, returns to Okta, and reaches the application only when assigned, and review the System Log for each sign-in.
    7. Plan for logout and user lifecycle changes. Sign-out and account deactivation in SectorLink do not automatically end sessions in Okta, so define how disabled users are removed from Okta.

     

    Because the design depends on the SectorLink protocol and attribute details, please open a case with Okta Support to review the architecture before you migrate users.

    We hope this helps you plan the federation approach for your organization.

     

     

    Regards.

    --

    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.

    Just released: More Okta Community badges just added

    Expand Post
    Selected as Best
This question is closed.
Loading
Can we federate our Okta instance to a non-Okta ID broker
Okta Support Agent (Beta)

Terms of Service

Hello! I'm the Okta Support Agent (Beta), your go-to resource for questions about Okta products. Please remember for your security and privacy, do not share any Personally Identifiable Information (PII) such as passwords, IP addresses, or other details with me.

Okta Privacy Policy and Terms of Service apply