<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
0D54z00006uRcjfCACOkta Classic EngineIntegrationsAnswered2021-04-12T22:45:32.000Z2021-04-09T16:20:54.000Z2021-04-12T22:45:32.000Z

JamesR.44275 (Customer) asked a question.

Separate tile for SAML integrated users and customers

I have a cloud service which I have created a 3rd-Party SAML integration for. The service has two separate URLs used for accessing the "Customer" front-end and another for the "Agent" front-end. It is not possible to configure two separate SAML integrations for the service. I would like to configure a Tile on the dashboard for access to all employees using the primary application integration, however I would like a second Tile targeted towards the agents and sending them to the Agent front-end. Is a bookmark the best way to handle this scenario?


  • Thank you for raising this question. This is Robert from Okta support.

     

    Yes, a bookmark app would be the best to handle this scenario.

     

    I would recommend the following KB regarding this matter. Even if it is referring to how to simulate Idp-initiated flow, it can be applied in your use case as well since you can have a bookmark app for the "Customer" front-end and one for the "Agent" front-end.

     

    https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Bookmark_App.htm 

     

    I hope my response helped. If you have further questions regarding this matter, please open a support case with us, and we will gladly assist you further.

     

    Expand Post
This question is closed.
Loading
Separate tile for SAML integrated users and customers