f7gvc (f7gvc) asked a question.
Hi Community.
My issue is: that after I created a free Developer account (providing both Google account integration and login + password) in Okta and activated it, when I try to log in to the Dev account's admin console, I get the 403 "Access Forbidden" error (no matter, using Google auth or login + password).
The context: my company uses Okta as a company's SSO for all employees, so I work in the environment with an active Okta session. Recently I've created the new Developer account in Okta as part of my testing activities. I successfully activated the account, but every time I try to log in there, I get a 403 error page. I tried different browsers and Private/Incognito windows. It doesn't help. Also, I cannot reset the password or delete that account, as well as create a new one (as my business email is used already for this one and Okta doesn't accept private emails for this type of accounts).
Please help me to find the root cause and fix the account, so I can finally continue with my testing.
Thanks in advance,
Kostiantyn
Hello @f7gvc (f7gvc) Thank you for posting on our Community page!
Please send us an email at community@okta.com with the Okta URL and your username and we will be able to provide assistance from that side
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.
Thanks @paul.stiniguta1.508386743840768E12 (Okta, Inc.),
I've contacted the Support team.
They told me that they can't see this account from their side, which is strange, as it is deployed and hosted on Okta servers...
But anyway, after some investigation, I found out that the activation process wasn't finished for this account:
I've set the password, but then I had to install and connect the Okta Verify app, but I wasn't redirected to this page (the password setup page was the last one for me). That is why later when I tried to log in to the account, I got the 403 page even after providing the correct credentials.
While the root cause was some network issue, that interrupted the account activation process, I think that the Okta team has to implement some fault-resistant backup for this case. Because now I have the dead-lock for the Okta Dev account on my email: it is already used for a Dev account, so I cannot register a new one, but also I cannot use the current account (or even remove it) as it is not accessible.