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

Very Strong password shows error message: "Your password must have a minimum strength of very strong"

      Summary

      This BUG is similar to the one that was fixed in ID-6561, except that here the interactive form shows "Very strong" and displays an error "Your password must have a minimum strength of very strong".

      Environment

      Steps to Reproduce

      1. Add the user to an authentication policy where the password strength requirement is "Very Strong"
      2. access id.atlassian.com with the test user
      3. enter the email and use the "Can't log in?" link to send a recovery link
      4. use the recovery link to try and reset the password
      5. try a password like "@ugu5t2023!!dd", for example
      6. this is reported as "Very strong"
      7. press continue

      Expected Results
      The password will change

      Actual Results
      You see the message error: "Your password must have a minimum strength of very strong"

      Workaround
      Use at least 12 characters with 3 capital letters and 3 special characters.

      Note
      Running some password checks show that the password used "@ugu5t2023!!dd" is "Strong". Therefore, it appears that the issue is in the "Very strong" info displayed when entering the new password.

            [ID-8602] Very Strong password shows error message: "Your password must have a minimum strength of very strong"

            Kat N made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Short Term Backlog [ 12074 ] New: Closed [ 6 ]

            Kat N added a comment -

            Hi everyone,
            Thank you for watching, following, and providing valuable feedback for our teams. Due to inactivity, we will be closing this bug as "Timed Out", but if this is still affecting your team, let us know so we can potentially re-evaluate.

            Kat N added a comment - Hi everyone, Thank you for watching, following, and providing valuable feedback for our teams. Due to inactivity, we will be closing this bug as "Timed Out", but if this is still affecting your team, let us know so we can potentially re-evaluate.
            Alfred A made changes -
            Labels New: guard-s6
            Meriem Dhahak made changes -
            Description Original: *Summary*

            This BUG is similar to the one that was fixed in ID-6561, except that here the interactive form shows "Very strong" and displays an error "Your password must have a minimum strength of very strong".

            Very strong password shows an error message: "Your password must have a minimum strength of very strong"

            *Environment*

            *Steps to Reproduce*
             # Add the user to an authentication policy where the password strength requirement is "Very Strong"
             # access id.atlassian.com with the test user
             # enter the email and use the "Can't log in?" link to send a recovery link
             # use the recovery link to try and reset the password
             # try a password like "@ugu5t2023!!dd", for example
             # this is reported as "Very strong"
             # press continue

            *Expected Results*
            The password will change

            *Actual Results*
            You see the message error: "Your password must have a minimum strength of very strong"

            *Workaround*
            Use at least 12 characters with 3 capital letters and 3 special characters.

            *Note*
            Running some password checks show that the password used "@ugu5t2023!!dd" is "Strong". Therefore, it appears that the issue is in the "Very strong" info displayed when entering the new password.
            New: *Summary*

            This BUG is similar to the one that was fixed in ID-6561, except that here the interactive form shows "Very strong" and displays an error "Your password must have a minimum strength of very strong".

            *Environment*

            *Steps to Reproduce*
             # Add the user to an authentication policy where the password strength requirement is "Very Strong"
             # access id.atlassian.com with the test user
             # enter the email and use the "Can't log in?" link to send a recovery link
             # use the recovery link to try and reset the password
             # try a password like "@ugu5t2023!!dd", for example
             # this is reported as "Very strong"
             # press continue

            *Expected Results*
            The password will change

            *Actual Results*
            You see the message error: "Your password must have a minimum strength of very strong"

            *Workaround*
            Use at least 12 characters with 3 capital letters and 3 special characters.

            *Note*
            Running some password checks show that the password used "@ugu5t2023!!dd" is "Strong". Therefore, it appears that the issue is in the "Very strong" info displayed when entering the new password.
            Meriem Dhahak made changes -
            Description Original: *Summary*

            This BUG is similar to the one that was fixed in ID-6561, except that here the interactive form shows "Very strong" and displays an error "Your password must have a minimum strength of very strong".

            Very strong password shows an error message: "Your password must have a minimum strength of very strong"

            *Environment*

            *Steps to Reproduce*
             # Add the user to an authentication policy where the password strength requirement is "Very Strong"
             # access id.atlassian.com with the test user
             # enter the email and use the "Can't log in?" link to send a recovery link
             # use the recovery link to try and reset the password
             # try a password like "@ugu5t2023!!dd", for example
             # this is reported as "Very strong"
             # press continue

            *Expected Results*
            The password will change

            *Actual Results*
            Jira gives you the message error: "Your password must have a minimum strength of very strong"

            *Workaround*
            Use at least 12 characters with 3 capital letters and 3 special characters.

            *Note*
            Running some password checks show that the password used "@ugu5t2023!!dd" is "Strong". Therefore, it appears that the issue is in the "Very strong" info displayed when entering the new password.
            New: *Summary*

            This BUG is similar to the one that was fixed in ID-6561, except that here the interactive form shows "Very strong" and displays an error "Your password must have a minimum strength of very strong".

            Very strong password shows an error message: "Your password must have a minimum strength of very strong"

            *Environment*

            *Steps to Reproduce*
             # Add the user to an authentication policy where the password strength requirement is "Very Strong"
             # access id.atlassian.com with the test user
             # enter the email and use the "Can't log in?" link to send a recovery link
             # use the recovery link to try and reset the password
             # try a password like "@ugu5t2023!!dd", for example
             # this is reported as "Very strong"
             # press continue

            *Expected Results*
            The password will change

            *Actual Results*
            You see the message error: "Your password must have a minimum strength of very strong"

            *Workaround*
            Use at least 12 characters with 3 capital letters and 3 special characters.

            *Note*
            Running some password checks show that the password used "@ugu5t2023!!dd" is "Strong". Therefore, it appears that the issue is in the "Very strong" info displayed when entering the new password.
            Meriem Dhahak made changes -
            Description Original: *Summary*

            This BUG is similar to the one that was fixed in ID-6561, except that here the interactive form shows "Very strong" and displays an error "Your password must have a minimum strength of very strong".

            Very strong password shows an error message: "Your password must have a minimum strength of very strong"

            *Environment*

            *Steps to Reproduce*
             # Add the user to an authentication policy where the password strength requirement is "Very Strong"
             # access id.atlassian.com with the test user
             # enter the email and use the "Can't log in?" link to send a recovery link
             # use the recovery link to try and reset the password
             # try a password like "@ugu5t2023!!dd", for example
             # this is reported as "Very strong"
             # press continue

            *Expected Results*
            The password will change

            *Actual Results*
            Jira gives you the message error: "Your password must have a minimum strength of very strong"

            *Workaround*
            Use at least 12 characters with 3 capital letters and 3 special characters.

            *Note*
            Running some password checks show that the password used "@ugu5t2023!!dd" is "Strong". Therefore, it appears that the issue is in the "Very strong" info displayed when entering the new password and before hitting "Save".
            New: *Summary*

            This BUG is similar to the one that was fixed in ID-6561, except that here the interactive form shows "Very strong" and displays an error "Your password must have a minimum strength of very strong".

            Very strong password shows an error message: "Your password must have a minimum strength of very strong"

            *Environment*

            *Steps to Reproduce*
             # Add the user to an authentication policy where the password strength requirement is "Very Strong"
             # access id.atlassian.com with the test user
             # enter the email and use the "Can't log in?" link to send a recovery link
             # use the recovery link to try and reset the password
             # try a password like "@ugu5t2023!!dd", for example
             # this is reported as "Very strong"
             # press continue

            *Expected Results*
            The password will change

            *Actual Results*
            Jira gives you the message error: "Your password must have a minimum strength of very strong"

            *Workaround*
            Use at least 12 characters with 3 capital letters and 3 special characters.

            *Note*
            Running some password checks show that the password used "@ugu5t2023!!dd" is "Strong". Therefore, it appears that the issue is in the "Very strong" info displayed when entering the new password.

            Hi mdhahak@atlassian.com I have created a backlog task for us to fix this: https://hello.jira.atlassian.cloud/browse/KIRBY-6339 I will push for it to get picked up this upcoming sprint.

             

            Regards,

            Janith

            Janith Randeniya (Inactive) added a comment - Hi mdhahak@atlassian.com I have created a backlog task for us to fix this: https://hello.jira.atlassian.cloud/browse/KIRBY-6339 I will push for it to get picked up this upcoming sprint.   Regards, Janith
            Janith Randeniya (Inactive) made changes -
            Assignee New: Janith Randeniya [ 018754bcb63f ]
            Janith Randeniya (Inactive) made changes -
            Development Effort New: S [ 13031 ]
            Preventable by New: Pre-deployment testing [ 19131 ]
            Was this caused by a recent change? New: No [ 19032 ]
            Status Original: Needs Triage [ 10030 ] New: Short Term Backlog [ 12074 ]
            SET Analytics Bot made changes -
            Support reference count New: 1

              018754bcb63f Janith Randeniya (Inactive)
              mdhahak@atlassian.com Meriem Dhahak
              Affected customers:
              0 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: