Meaning Of The BLOCKED(BRUTEFORCE) User Status In Auth0

Overview

The BLOCKED(BRUTEFORCE) status appears on the user details page of the Auth0 dashboard when Brute Force Protection blocks a specific identifier due to consecutive failed login attempts. Auth0 displays this status when the blocked identifier matches the email, username, phone number, or specific substrings associated with the user account.


User 

Applies To

  • Auth0
  • User Details
  • Brute Force Protection

Solution

What does the BLOCKED(BRUTEFORCE) status mean?

The BLOCKED(BRUTEFORCE) status indicates that Brute Force Protection blocked the user. Sometimes, the specific identifier that Auth0 blocks is not obvious.

How does Brute Force Protection block identifiers?

When the Brute Force Protection feature blocks an identifier, the existence of the user account bound to the identifier does not matter. Because consecutive failed login attempts trigger Brute Force Protection, Auth0 cannot determine if the user exists during a failed login.

Identifiers checked by the dashboard

The user details page of the tenant dashboard checks specific identifiers to determine if the user displays as BLOCKED(BRUTEFORCE). Auth0 checks the following identifiers:

  • The email of the user account.
  • The username of the user account.
  • The phone_number of the user account.
  • The local part of the email of the user account.

Examples of identifier checks

Review the following examples to understand how Auth0 checks the local part of the email and the user ID substring:

  • If the email address is user@example.com, Auth0 checks the local part of the email, which is the string user.
  • Auth0 checks the substring after the last pipeline (|) character of the user_id. If the user_id is ad|ad_connection|user, the identifier used to check for blocks is user.

NOTE: The last two conditions primarily apply to users of Active Directory (AD) and Lightweight Directory Access Protocol (LDAP) connections.

Recommended content

No recommended content found...