<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
0D54z00007gejz7CAAOkta Classic EngineDirectoriesAnswered2024-04-16T12:33:36.000Z2022-05-27T10:04:17.000Z2022-05-30T15:26:54.000Z

sipo1 (sipo1) asked a question.

Why the profile mappings need to be configured both ways?

I have created a Slack App, but I am a little bit confused with the Profile Mappings. As far as I know, I just need to set the OKTA -> Slack mappings. I wonder under what circumstances do I need to set the Slack -> OKTA mappings.

 

BTW, if I created an IdP, under what circumstances do I need to set the OKTA -> IdP mappings.

Image is not available


  • Hi @sipo1 (sipo1)​ , Thank you for reaching out to the Okta Community!

     

    These options are available for all apps to cover possible requirements and use cases. For some apps, attribute write-back is required. For example Huma Resources Management apps would be the ones managing the user's profile in Okta. 

    It's not mandatory to configure that in your case if you're planning to manage your users in Okta and then push the data to Slack.   

     

     

    Hope this clarifies things!  

    Expand Post
  • sipo1 (sipo1)

    Thanks for your reply. But how to write-back the attribute, by OKTA open api or some standard protocol? Are there any specific apps need this configuration so that I can try it?

This question is closed.
Loading
Why the profile mappings need to be configured both ways?