<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
0D54z0000AIIrIbCQLOkta Classic EngineUniversal DirectoryAnswered2024-12-31T18:20:22.000Z2024-12-31T07:15:04.000Z2024-12-31T18:20:22.000Z
Unable to log into Admin account | We found some errors. Please review the form and make corrections.

I added a few custom attributes in the Profile Editor for 'User (default)', where the 'Attribute Required' is checked, and the user permission is set to 'Read-Write'. After logging out and logging back into the admin account, I enter my credentials, receive a push notification on Okta Verify, and then encounter a third window that asks me to add custom attributes. Regardless of the information I enter, I receive the following error: 'We found some errors. Please review the form and make corrections.' I also have another super admin account, and when I try to log in with that account, I get the same error."

 

/help/servlet/rtaImage?refid=0EM4z000008eTZu 

The url is: [redacted by moderator]

 

I have a few regular user accounts, and I am getting the same error message.

I am unable to contact support using the domain [redacted by moderator], so I had to create another developer account to reach out and post a question here.

Please help me.

 


  • Hi @User17029574962983902672 (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. It seems you have made a configuration change that broke the authentication flow for all users. Without admin access, the configuration cannot be undone through self-service.   

     

    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.

    Expand Post
    Selected as Best
  • Hi @User17029574962983902672 (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. It seems you have made a configuration change that broke the authentication flow for all users. Without admin access, the configuration cannot be undone through self-service.   

     

    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.

    Expand Post
    Selected as Best
This question is closed.
Loading
Unable to log into Admin account | We found some errors. Please review the form and make corrections.