<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
0D54z00009M8iazCABOkta Classic EngineSingle Sign-OnAnswered2023-06-20T21:43:45.000Z2023-06-20T19:24:13.000Z2023-06-20T21:43:44.000Z

BenZ.81638 (Customer) asked a question.

How to configure an Okta admin to use SSO and still be able to access Okta Config

Hey folks -

We previously used Okta as a gateway into our application for clients (Okta connects to their IdP). We want to use this for our internal users as well who also use our application. However when we set that up, the users who use that application and configure Okta are no longer able to access the Okta Dashboard to make adjustments to configuration, they are always redirected to the application because of the routing rule.

 

What is the best solution here? Should those users just have an Okta Admin account with different credentials?


  • DonF.81354 (Customer)

    Hi! Great question. I will say that in my own org, we do use dedicated admin accounts for administering Okta, if for nothing else than to ensure security practices are as tight as possible. Assuming that is not an option or preferable in your case, I would recommend taking a look at the routing rules and seeing what can be done. You do have the option to filter based on user matches, so there are options available for a custom attribute potentially. Another is to filter based on the app being accessed, routing to a different IdP depending on which you care to filter on. All of those seem like reasonable possibilities, but please do make sure that I understand the scenario and that these suggestions work. Otherwise, please give me whatever further context you can and I would be happy to help further! Thanks!

    Expand Post
This question is closed.
Loading
How to configure an Okta admin to use SSO and still be able to access Okta Config