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

Based in (location) cannot be updated via user provisioning

XMLWordPrintable

      Issue Summary

      When connecting Atlassian Access to a third party identity service provider, the Based In (location) attribute of an Atlassian Account cannot be updated.

      Steps to Reproduce

      1. Enable Atlassian Access setup user provisioning
      2. Try to map a location attribute from the third party IDP into the location attribute in Atlassian.

      Expected Results

      It should be possible to map the location attribute into the Atlassian Account

      Actual Results

      The location attribute of a user cannot be mapped.

      On the managed account profile, the location attribute is blocked due to user provisioning

      Workaround

      The provisioned users can still fill in the details on Atlassian side.

        1. location.png
          location.png
          113 kB
        2. image-2021-05-21-12-24-18-735.png
          image-2021-05-21-12-24-18-735.png
          206 kB
        3. based in.png
          based in.png
          67 kB

              e902c0832f88 Sudesh Peram
              rmacalinao Ramon M
              Votes:
              71 Vote for this issue
              Watchers:
              74 Start watching this issue

                Created:
                Updated:
                Resolved: