<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
0D5KZ000019vHKx0AMOkta Classic EngineAdministrationAnswered2025-10-23T19:40:25.000Z2025-08-13T11:24:58.000Z2025-10-23T19:40:25.000Z
How to Contact support for assistance

I created a free integrator account. While exploring the features I deleted the Okta Verify option from the instance's security policy as admin. I am the only user and admin in this instance.

 

Subsequently I get this error

 

"Unable to sign in. Contact support for assistance."

 

It appears that I am not able to open a case for support either.

 

"You Do Not Have Access to Create a Case"

 

Any suggestions on how to get support to restore the admin account?

 

imageimage


  • RohitU.50441 (Trevonix)

    I don't think support access is allowed for free integrator tenants.

     

    Support channels are mostly open for customers with live production orgs.

     

    May be you can post questions/queries here if you think those can be addressed here.

     

     

    Expand Post
  • DianaL.19788 (Customer Support Online Community and Social Care)

    Hello @JuntaoZ.72428 (Customer)​ , thank you for contacting Okta Community.

     

    The error you see is most often encountered by admins who have disabled the only MFA available for admin users in the org. For more details, please see the following:

    Okta will Require Multi-Factor Authentication (MFA) to Access the Okta Admin Console

    Frequently Asked Questions on MFA Enforcement for the Admin Console

     

    If you lose access to your org's Admin Console, the only way to resolve this is with a support ticket. Opening a support ticket is a feature available to paid accounts. You can read more about it in the Workforce Identity Cloud Free Trial Account Support Policy Change article.

     

    If you have a paid production 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). If those options are not available for you despite having a paid account, please contact your Okta Account Executive or Customer Success Manager, and they will be able to engage the Support team on your behalf. 

     

    Unfortunately, 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. You may need to use a different email address.

     

    Alternatively, if you do not have a paid account but are interested in getting one, you can contact our Sales team. A paid account could be used to request assistance for a connected free account, but the Sales team would have more details on that. 

     

    Regards. 

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Just released: More Okta Community badges just added

    Expand Post
    Selected as Best
    • DianaL.19788 (Customer Support Online Community and Social Care)

      Hello @AshutoshR.64185 (Customer)​ , if you lose access to your org's Admin Console, the only way to resolve this is with a support ticket. Opening a support ticket is a feature available to paid accounts. You can read more about it in the Workforce Identity Cloud Free Trial Account Support Policy Change article.

       

      If you have a paid production 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). If those options are not available for you despite having a paid account, please contact your Okta Account Executive or Customer Success Manager, and they will be able to engage the Support team on your behalf. 

       

      Unfortunately, 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. You may need to use a different email address.

       

      Alternatively, if you do not have a paid account but are interested in getting one, you can contact our Sales team. A paid account could be used to request assistance for a connected free account, but the Sales team would have more details on that. 

       

      Regards. 

      --

      Help others in the community by liking or hitting Select as Best if this response helped you.

      Expand Post
  • RenaudR.90806 (Customer)

    Good morning,

     

    Same issue here.

     

    If Okta Verify is required for Admin, Admin shouldn't be able to disable Okta Verify from Security policy. That makes no sense.

     

    No more access to my integrator plan. No right to create a ticket in Okta Digital Experience interface. No communication received for Developer to Integration plan migration.

     

    Any help on this subject?

     

    Thanks in advance.

    Expand Post
    • RohitU.50441 (Trevonix)

      @RenaudR.90806 (Customer)​  it is not that Okta verify is mandatory to admins.

       

      MFA is mandatory in order to access admin console. Hence policies should be defined granularly for end users and admins.

       

      At least one factors should be enabled and forced for admins to be able to login to admin console.

      This is inline with the security standards expected for previleged access.

      More info here -

      https://support.okta.com/help/s/blog/a674z000000147HAAQ/mfa-enforcement-for-the-admin-console?language=en_US

       

      If you are locked out, you should be able to get this resolved by support if you are not paid license.

       

      If not, you are free to register other integrator tenants. Make sure MFA is not disabled for Admin console/Admin users.

      Expand Post
  • RenaudR.90806 (Customer)

    Good morning,

    Thanks for the reply.

    I understand MFA is mandatory for admin access.

    I wanted to point out that disabling Okta Verify from Security policy shouldn't impact admin accounts. Applying this change blocked my admin account.

    This is a simple test case that should have been yet implemented on Okta side.

    Best regards.

    Expand Post
This question is closed.
Loading
How to Contact support for assistance