<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
0D5KZ00000cFpUb0AKOkta Classic EngineIntegrationsAnswered2025-04-30T17:44:53.000Z2025-04-03T14:34:15.000Z2025-04-30T17:44:53.000Z

RajeshD.00986 (Customer) asked a question.

How can we get a Custom attribute(name of the source idp) to the target Okta org

we have an application where this will be authenticated from different IDP's profile.

we would like to have some custom attribute on a profile from where the profile was sourced(from which IDP), the profiles were created in target IDP via JIT provisioning.

is there a way to introduce the custom attribute to know the source of the profile.

Any documentation is available on how to achieve this .


  • @RajeshD.00986 (Customer)​ 

    Let me make sure I am getting this correctly .

    Your user is authenticating against some other (third party IDP) and sending an SAML assertion to okta.. You want to consume assertion and JIT user along with custom attribute (IDP Source). correct?

     

    In that case you can setup an Identity Provider in Okta (security->Identity Provider) and enable JIT (inbound SAML) and use the profile mapping to map the values from IdP User Object to Okta User Profile.. Here I am making an assumption that your assertion contains the source thirdparty Idp value.

     

    More info about this below

    https://help.okta.com/en-us/content/topics/security/idp-add-saml.htm

     

    Please let us know if this is what you are looking for

     

    HTH

    -Bala

    Expand Post
    Selected as Best
  • @RajeshD.00986 (Customer)​ 

    Let me make sure I am getting this correctly .

    Your user is authenticating against some other (third party IDP) and sending an SAML assertion to okta.. You want to consume assertion and JIT user along with custom attribute (IDP Source). correct?

     

    In that case you can setup an Identity Provider in Okta (security->Identity Provider) and enable JIT (inbound SAML) and use the profile mapping to map the values from IdP User Object to Okta User Profile.. Here I am making an assumption that your assertion contains the source thirdparty Idp value.

     

    More info about this below

    https://help.okta.com/en-us/content/topics/security/idp-add-saml.htm

     

    Please let us know if this is what you are looking for

     

    HTH

    -Bala

    Expand Post
    Selected as Best
This question is closed.
Loading
How can we get a Custom attribute(name of the source idp) to the target Okta org