<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
0D51Y00006OE8e1SADOkta Classic EngineSingle Sign-OnAnswered2024-08-11T09:01:57.000Z2019-06-27T19:40:52.000Z2019-07-01T17:33:00.000Z

xmihr (xmihr) asked a question.

How to setup Attributes externally as an Identity Provider (SSO) thru Okta Interface

We are working as Identity Provider and use the service of Service Provider thru SSO by Okta. Our application has many sub systems and have different variable attributes (user, system details etc), which I think we can not set statically (thru user profile or attribute setup interface).

 

So, I wanted to know about setting attributes externally. Is it possible to feed in attributes from another application to Okta ?


  • StevenJ.49766 (Customer)

    I believe the answer is that you have to conduct multiple manual mappings of attributes for each application that you setup within Okta, one for each use case. But each attribute moving from Okta to the application . So in the following example where userName = userName in the application, but another subsystem wants userName = user.example1 you could have the userName attribute described twice, on separate attribute lines. However, this does not work in reverse. You can't have a subsystem ask Okta for a specific attribute named userName and expect the system to provide two different values for userName. Within Okta userName is a singular object. Even if your application and its associated subsystem has userName but expects different source values contextually based on where it is within the application.

    Expand Post
    Selected as Best
  • StevenJ.49766 (Customer)

    I believe the answer is that you have to conduct multiple manual mappings of attributes for each application that you setup within Okta, one for each use case. But each attribute moving from Okta to the application . So in the following example where userName = userName in the application, but another subsystem wants userName = user.example1 you could have the userName attribute described twice, on separate attribute lines. However, this does not work in reverse. You can't have a subsystem ask Okta for a specific attribute named userName and expect the system to provide two different values for userName. Within Okta userName is a singular object. Even if your application and its associated subsystem has userName but expects different source values contextually based on where it is within the application.

    Expand Post
    Selected as Best
This question is closed.
Loading
How to setup Attributes externally as an Identity Provider (SSO) thru Okta Interface