Uploaded image for project: 'Atlassian Access'
  1. Atlassian Access
  2. ACCESS-771

Unable to edit "Based in" field when SCIM is enabled

    XMLWordPrintable

Details

    Description

      Disclaimer

      This difficulty was already described in another Bug report (ACCESS-766) therefore, to avoid confusion, this one will be closed. Please keep tracking this issue on ACCESS-766.

      Apologies for the inconvenience.

      Issue Summary

      The Based in field is gets locked out on Managed accounts of a Organization when the SCIM integration is enabled.

      However, the SCIM does not support that field yet (there is no matching Target attribute) therefore, the admins can edit that through the IdP sync neither at the Org side.

      Steps to Reproduce

      1. Integrate with SCIM
      2. Try to update that field at Org > Directory > Managed accounts > User profile or at the IdP.

      Expected Results

      The field would get updated through the SCIM integration.

      Actual Results

      1. The SCIM does not support the field.
      2. The admins can't change that manually due to the integration.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. ACCESS-766 Based in (location) cannot be updated via user provisioning

          • Medium - Medium priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              jnunes@atlassian.com João Nunes
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: