-
Bug
-
Resolution: Fixed
-
Highest
-
None
-
55
-
Minor
-
Issue Summary
Users still can edit Full name, Job title, Department, Timezone and Organization fields on their Atlassian Accounts details at https://id.atlassian.com/manage-profile even when user provisioning is enabled. This should not happen and might be disruptive to the company since the information may not reflect the information that is on their internal directory.
Steps to Reproduce
- Enable User provisioning
- Sync a user
- Ask the user to access https://id.atlassian.com/manage-profile and change one of those fields
When the user does this manual change it overwrites the field. Unless the IdP sends a PATCH to update that information the field won't reflect the IdP information.
Expected Results
When User provisioning enables the users should not be able to edit those fields. The Org admins which should have that ability for edge cases don't have.
Actual Results
The users can edit them.
Workaround
To get the information reflecting the IdP side you should trigger a change on the users' profile there. Each IdP implemented the User provisioning REST API differently so it is recommended that you engage their support team gets more details on how they trigger those updates.
- duplicates
-
ID-7820 Restrict users edition when the account is synced through User Provisioning
- Closed
-
ID-8619 Improve the pagination and name convention so it can be more consistent across all API endpoints
- Closed
- is duplicated by
-
ACCESS-1220 SCIM synced accounts are able to modify some of their own SCIM syncable attributes
- Closed
-
ID-7820 Restrict users edition when the account is synced through User Provisioning
- Closed
- is action for
-
IAM-55 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...