Uploaded image for project: 'Identity'
  1. Identity
  2. ID-6169

Option to lock user out after maximum failed password attempts

    • Icon: Suggestion Suggestion
    • Resolution: Tracked Elsewhere
    • None
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently, after 5 failed login attempts, the user is presented with a CAPTCHA.
      However, the user is still able to continue with the login attempts (as long as the correct CAPTCHA is entered)

      It is not possible to set a maximum number of failed password attempts and lock the user out.
      We need to allow site-admins the ability to completely lock the account after a number of failed attempts

            [ID-6169] Option to lock user out after maximum failed password attempts

            see ID-80. Nuanced password and security settings are best managed in SAML integrations.

            MFB (Inactive) added a comment - see ID-80 . Nuanced password and security settings are best managed in SAML integrations.

            We believe features like this are best handled by the company at their own IDP and can then use SAML integration to allow their managed users access to Atlassian sites.

            MFB (Inactive) added a comment - We believe features like this are best handled by the company at their own IDP and can then use SAML integration to allow their managed users access to Atlassian sites.

            The account lockout is a very important security requirement for most companies. Please add this as a feature to the Password Policy.

            Marianne Naughton added a comment - The account lockout is a very important security requirement for most companies. Please add this as a feature to the Password Policy.

              Unassigned Unassigned
              dsjauwmook davy
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: