Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-1042

The user search to add members to an authentication policy is not working properly when searching for email addresses

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • PLAT - Hydra
    • None

      Issue Summary

      According to the Authentication Policies documentation, when adding new users to a policy, Org admins should be able to search by the user's email address, or by the user's name. However, the search for email address is not working properly. 

      Steps to Reproduce

       Make sure you have an Organisation with an Atlassian Access subscription and a verified/claimed domain.

      1. Access the Org administration.
      2. Click on Security, on the top navigation bar.
      3. Click on Authentication Policies, on the sidebar.
      4. Edit a policy (create a new one if needed).
      5. Navigate to the Members tab.
      6. Click on Add members button.
      7. Paste the exact email from the user.

      Expected Results

      The search should return only the specific user. 

      Actual Results

      The search return users that aren't matching the input field. Besides, if you delete the last letter from the email (let's say the m from .com), the search won't return any user.

      Workaround

      You should be able to find the user searching for their name, instead of their email address. Make sure to search for the entire name (for example, searching for Vi won't return a user named Vitor - you would need to search for Vitor).

            [ACCESS-1042] The user search to add members to an authentication policy is not working properly when searching for email addresses

            @Kat N
            It would be great if this could include inactive users as well.  We do need to reactivate quite often and if we can find them in the UI as opposed to doing an export it would be great.  It sounds like if we can't find them, we will need to export and then reactivate using the API?

            Cathy Soller added a comment - @Kat N It would be great if this could include inactive users as well.  We do need to reactivate quite often and if we can find them in the UI as opposed to doing an export it would be great.  It sounds like if we can't find them, we will need to export and then reactivate using the API?

            Kat N added a comment -

            Managed account search improvements that rolled out at the beginning of this month have fixed this issue. Please note that deactivated accounts will not be shown in the user search - in this case, the CSV feature can be used to move users to an auth policy. If this is not sufficient for your workflow, let us know in the comments and I will create a feature request to track this work. 

            Kat N added a comment - Managed account search improvements that rolled out at the beginning of this month have fixed this issue. Please note that deactivated accounts will not be shown in the user search - in this case, the CSV feature can be used to move users to an auth policy. If this is not sufficient for your workflow, let us know in the comments and I will create a feature request to track this work. 

              fe351cdb72b6 Gaurang Kher
              edc026a7b429 Vitor A (Inactive)
              Affected customers:
              7 This affects my team
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: