<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
0D54z0000A3qhPBCQYOkta Classic EngineAuthenticationAnswered2025-04-24T09:00:15.000Z2024-03-23T13:10:29.000Z2024-04-01T14:37:42.000Z

0vtud (0vtud) asked a question.

In OKTA IDE can we change the order of authentication to do OKTA verify first, before password based authentication to avoid password spray attack

We are seeing lot of password spray attacks locking users in AD through Cisco VPN radius integration. We want to change the order of authentication (okta verify- MfA first followed by password based authentication).


  • User16594883467582706479 (Customer Support Online Experience)

    Hi, @0vtud (0vtud)​ 

     

    Thank you for posting on our Community page!

     

    Basically, the password spray attacks are at the basic authentication level and not on browser. 

    Here is some more info on the basic auth: https://developer.okta.com/books/api-security/authn/api-authentication-options/

     

    If you only see basic authentication, in the System logs, on /authn endpoint that fails with invalid credentials, MFA is not being evaluated, as the authentication is not happening in a modern environment, like a browser in which MFA can be triggered.

     

    This type of attack is not manageable by adding a factor sequence, but can be better checked if you enable ThreatInsight.

     

    I advise you to open a case with Support so they can take a look at the logs and offer a customised solution. 

     

    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
    Selected as Best
  • User16594883467582706479 (Customer Support Online Experience)

    Hi, @0vtud (0vtud)​ 

     

    Thank you for posting on our Community page!

     

    Basically, the password spray attacks are at the basic authentication level and not on browser. 

    Here is some more info on the basic auth: https://developer.okta.com/books/api-security/authn/api-authentication-options/

     

    If you only see basic authentication, in the System logs, on /authn endpoint that fails with invalid credentials, MFA is not being evaluated, as the authentication is not happening in a modern environment, like a browser in which MFA can be triggered.

     

    This type of attack is not manageable by adding a factor sequence, but can be better checked if you enable ThreatInsight.

     

    I advise you to open a case with Support so they can take a look at the logs and offer a customised solution. 

     

    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
    Selected as Best
This question is closed.
Loading
In OKTA IDE can we change the order of authentication to do OKTA verify first, before password based authentication to avoid password spray attack