-
Bug
-
Resolution: Duplicate
-
Medium
-
None
-
31
-
Severity 3 - Minor
-
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
- Enable Atlassian Access setup user provisioning
- 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.
- As the end user, login to Atlassian and access https://id.atlassian.com/manage-profile/profile-and-visibility
- Edit the Based In information.
- duplicates
-
ACCESS-822 Support more synced attributes for SCIM User Provisioning
- In Progress
- is duplicated by
-
ACCESS-771 Unable to edit "Based in" field when SCIM is enabled
- Closed
-
ACCESS-744 Provisioning: Add support for an attribute mapped to extended_profile.location
- Closed
- is related to
-
MOVE-25435 Loading...