-
Bug
-
Resolution: Timed out
-
Low
-
None
-
2
-
Minor
-
Issue Summary
A user deactivated via IDP can be reactivated by org admin without IDP intervention.
Steps to Reproduce
- Synced a user via OKTA.
- Deactivated this user via Okta. This deactivated the Atlassian account and marked the SCIM record as false.
- Marked this user for deletion and canceled deletion via managed accounts.
- This reactivated the Atlassian account, and the SCIM record was still marked as false. User account stays in the locked state, i.e., managed via IDP.
Expected Results
We should revert the Atlassian account to the previous state on canceling user deletion, i.e., deactivated state. As IDP manages the user account, we should allow reactivation of the account only via IDP.
Actual Results
User accounts get reactivated, and SCIM record for the same stays inactive. However, the user account still shows managed via IDP under the managed accounts.
Workaround
Will update the workaround as soon as available.
[ACCESS-1382] User deactivated via IDP can be reactivated from org
| Workflow | Original: JAC Bug Workflow v3 [ 4132353 ] | New: JAC Bug Workflow v4 [ 4567744 ] |
| Resolution | New: Timed out [ 10 ] | |
| Status | Original: Long Term Backlog [ 12073 ] | New: Closed [ 6 ] |
| Component/s | Original: Identity Internal - SCIM [ 56703 ] | |
| Component/s | New: User Sync - SCIM Maintenance [ 66413 ] | |
| Key |
Original:
|
New:
|
| Project | Original: Identity [ 16810 ] | New: Atlassian Access [ 18910 ] |
| Support reference count | Original: 1 | New: 2 |
| Support reference count | New: 1 |
| Status | Original: Gathering Impact [ 12072 ] | New: Long Term Backlog [ 12073 ] |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
Hi everyone,
Thanks for following and watching this bug for updates. Due to inactivity over the past year, we are closing this issue as "Timed Out", but if this bug is still impacting your team, please leave a comment for us to review.