• Public

Multi-Factor Authentication

Skip Feed

  1. IsaacB.81593 (Customer)

    October 9, 2026 at 12:34 PM

    Question about the EA Authenticator Sets feature and "legacy API integrations."

     

    There's an EA feature for authenticator enrollment "Authenticator Sets." You can set up emrollment policy where a user can choose from a menu of authenticators, but must enroll in a specified number. This brings to OIE a feature that Classic had.

     

    There appears to be a catch, though. With the EA feature enabled, when you try to add a new enrollment policy, you're given a choice: "Authenticator Sets" or "Legacy." The Legacy option comes with a caption: "Use if you have legacy API integrations." I did not find reference in the documentation what counts as a "legacy API integration." Could this be:

    • An API token created before the policy is added?
    • Use of an OAUTH authorization server?
    • Org2Org with the OAUTH provisioning method?
    • API service apps?

    What is the impact of creating an Authenticator Set if I have a "legacy API integration" in my environment? Will the integration break because the Authenticator Set policy will prompt the service to enroll for MFA?

     

    Thanks,

    Expand Post
    • 2 comments
    • 16 views
    1 of 2

    • IsaacB.81593 (Customer)

      Thank you, Paul. So in this case "legacy API" refers to custom apps that do user authentication.

  2. SujaE.90746 (Customer)

    June 25, 2026 at 5:11 AM

    Hi , need assistance with resetting the Okta MFA for an admin user account. I no longer have access to the previously configured device, as the phone with the Okta Verify app has been lost.

    Due to this, I am unable to complete the authentication process. Could you please help reset or reconfigure the MFA so I can set it up on a new device?

    Please let me know if any additional verification or information is required from my end.

    • 1 comment
    • 68 views

    • Paul S. (Okta, Inc.)

      Hello @SujaE.90746 (Customer)​ Thank you for posting on our Community page!

       

      If you are an employee, contractor, patient, student, or client of a company, institution, or service provider that requires you to use Okta Verify, please contact the company's, institution's, or service provider's IT support or Help Desk team.

       

      While Okta provides the Product (Okta Verify app), your company, institution, or service provider handles individual account management (like MFA reset or password management) and access policies (such as recovery options or alternative factors).

       

      Please contact your company's or service provider's IT support or Help Desk so they can review your account information and provide further assistance.

       

      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.

      Expand Post

  3. PramendraK.19393 (Customer)

    May 5, 2026 at 3:08 AM

    Hi, we are seeing quite a lot of the MFA Failure notifications like these ones below, and originating from different countries, what does this mean and how to stop it please? Thank you

     

    image

    • 1 comment
    • 89 views

  4. IsaacB.81593 (Customer)

    February 28, 2026 at 8:03 PM

    Can Fido enrollment be simplified? Am I missing something?

     

    It seems to me that one used to be able to enroll a Fido factor (security key or print reader) by just choosing that option from the available authenticators and following simple prompts. This appears to have gotten more complex. I'm trying to enroll a physical key in Chrome.

     

    Prompt 1. "Create a passkey." 

    [I tried adding a screenshot, but app won't let me save the post]

     

    As an end-user, I'd be asking "what's a passkey and I don't have time to learn what it is." Hit "continue" and I'm being prompted by my browser's print reader and it enrolls the print reader. Never offers to enroll the key.

     

    Try "Save another way." 

     

    Prompt 2 "Choose where to save..."

    [I tried adding a screenshot, but app won't let me save the post]

     

    I figure the third choice makes sense, but I'd hate to be an end user, or the team that supports them.

     

    Prompt 3. QR code or key. 

    [I tried adding a screenshot, but app won't let me save the post]

     

     

    I tap the key and get enrolled. But can I keep that QR code away from my end users and simplify their path?

     

    We have "Block synced passkeys for FIDO2 (WebAuthn) Authenticators" enabled. Org is Classic. Device is Mac Sequoia. Browser is Chrome, 100% up-to-date.

     

    Thanks.

    Expand Post
    • 1 comment
    • 90 views

    • Paul S. (Okta, Inc.)

      Hello @IsaacB.81593 (Customer)​ Thank you for posting on our Community page!

       

      Enrolment should be straight forward, maybe something has been miss-configured or additional steps added to the enrolment. please see our doc below:

      https://help.okta.com/oie/en-us/content/topics/identity-engine/authenticators/configure-webauthn.htm

       

      If there are still issues I would recommend to Open a case with Support for additional assistance.

       

      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.

      Expand Post

  5. Christina.J (Okta)

    February 9, 2026 at 10:15 PM

    Did you miss our insightful Ask Me Anything session with an Okta product expert on Multi-

    Factor Authentication? Don’t worry—we’ve got you covered!

     

    Our recent Ask Me Anything session on adopting stronger multi-factor authentication (MFA) with Okta's product expert was packed with engaging discussions and valuable insights. If you missed it, don’t worry—we’ve rounded up the top highlights for you! Discover key takeaways on getting started, best practices, use cases, and more. Read the recap.

    • 100 views
    Paul S. and Mihai N. like this.

  6. Christina.J (Okta)

    January 29, 2026 at 11:31 PM

    Is your MFA truly phishing-resistant? 🔐

     

    Our new technical deep dive on Okta FastPass details how Possession-Based Authentication, utilizing Cryptographic Binding and Origin Binding, combats AiTM attacks.

     

    Learn about the architectural mechanics, best practices for Global Session and Authentication Policy in OIE, and a strategic framework for a scalable, zero-friction passwordless rollout.

    • 1 comment
    • 115 views
    Paul S. and Mihai N. like this.

    • Paul S. (Okta, Inc.)

      Great deep dive—Origin Binding is key!

  7. Christina.J (Okta)

    January 21, 2026 at 8:08 PM

    Check out the January Okta Community Monthly Buzz! 

    This month's edition features helpful insights from @John Cokkinias (Okta)​ on our recent Ask Me Anything (AMA) on MFA, details on the improved Okta Customer Success Hub, training and certification updates, member shout-outs, how-to support resources, new product features, and more. You can check out the latest and greatest highlights from our January Monthly Buzz here.

    • 86 views
    Mihai N. likes this.

  8. MarcusM.35725 (Customer)

    January 13, 2026 at 1:20 AM

    I need someone to contact me regarding two sources of MFA that are hitting my phone.

    I have 2 separate shortcode text MFA that I get, and they are NOT from anything I am doing. Both shortcodes "Help" direct me to Okta phone numbers, but I cannot interact because I am NOT a customer. Please someone contact me and help me find out which of these MFA codes are being sent to me from where so I can secure the login further. Text reads: ###### is your verification code. Valid for 5 minutes. No idea which company or where it comes from, only from Okta hosting the shortcode.

    • 1 comment
    • 95 views

End of Feed
End of Feed
8 Chatter Feed Items

Group Details

Details