
nsico (nsico) asked a question.
When our super admins are accessing our company orgs we use a federated (Azure) ID. Logging in is redirected through Azure through some logic.
However the problem here is that Okta does not manage the passwords for these accounts so when performing an action that Okta considers "Protected" we will be redirected back to the Okta password page where the federated password simply does not work.
What is the expected solution for these scenarios? It is not reasonable to expect to use or manage a special Okta managed account to perform certain admin functions. What other solution should admins in this scenario consider to get around this?

Hello @nsico (nsico) Thank you for posting on our Community page!
For this type of situations the only option in this case is to set a password for the users in question so that they can verify who the are. I understand that this might not be the desired outcome but in order to verify their account a password is needed for these type of actions.
However you can add a Feature Request on our Idea section, for a chance that this functionality to be added in the future.
https://support.okta.com/help/s/ideas
Thank you for reaching out to our Community and have a great day!
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Ask Us Anything thru 7/14: Okta WIC leadership want to hear from you