User1733273389766401629 (Customer) asked a question.
When attempting to sign in to the admin console, I am getting:
Sign In Denied
You do not have permission to access your account at this time. If you're wondering why this is happening, please contact your administrator.
Naturally, I am the (only) administrator of this developer account. It is not caused by incorrect credentials, as a different error is presented when invalid credentials are input; this error only appears when using the correct credentials.
I submitted a support case in late November and was informed that this was because MFA had not been set up on the admin account, and as a result, access was disabled when MFA became required. Support restored the ability to log in, and I immediately set up MFA and was able to access the admin console with no issues.
Three weeks later, I am now locked out with this same error again, despite having MFA in place. Support is now refusing any follow-up assistance via the ticketing system, citing a change in policy that requires all developer org related issues to be submitted here.
What is the best path forward to resolving this error?
Hi @User1733273389766401629 (Customer) , Thank you for reaching out to the Okta Community!
Please note that free developer/trial accounts are only recoverable via self-service provided that you have configured the appropriate policies and backup accounts.
If you have a paid production/developer account with us, please leverage it to open a case via the support.okta.com site or call the support line (Customer Support Account ID number required) so our Okta Support colleagues can review the matter. If for whatever reason those options are not available for you, please contact your Okta Account Executive or Customer Success Manager, and they will be able to engage the Support team on your behalf.
If no paid developer or production account is available, the only option left is to sign up for a new free trial or developer account and leverage those for testing.
Beyond that, engaging our Okta Sales team to discuss the matter would be the only option as it is unfortunately completely outside of the Okta Community Team's scope.
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Hello - thank you for the reply. This account was working perfectly fine until Okta took action to disable it. I haven't forgotten the password. I have not broken any configurations or otherwise locked myself out. Okta took action, without notice or communication, to disable this otherwise functional account. Leaving me without any avenue to contact Okta, whether via support or Community, to remedy the problems which Okta itself has caused is an unacceptable non-resolution. If your suggestion is that Okta can simply break orgs at a whim, and decline to provide any sort of support in such circumstances to resolve issues which Okta caused and only Okta can resolve, resulting in developer time and work being lost with no recovery options besides starting all over... this is an untenable position for partner developers to operate from.