How to clear out the SCIM record for a de-provisioned account?

Still need help?

The Atlassian Community is here for you.

Ask the community


Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.


Purpose

After a managed account has been de-provisioned, the Atlassian Account will remain on a deactivated state and will remain to be locked by the user provisioning feature. There will be cases where that account needs to be re-activated but should remain out of the provisioning scope. ie. The account is required for Trello or Bitbucket access. 

Solution

To allow manual reactivation by organization administrators, the managed account can be unlocked by removing the underlying SCIM record ( ACCESS-1021 - Getting issue details... STATUS ). The following procedure can be used to achieve this. 

  • Retrieve the SCIM ID of the de-provisioned account.

    SELECT * FROM users;
  • If you're suggesting the use of SQL INSERT UPDATE DELETE operations please include the following warning:

    Always back up your data before performing any modifications to the database. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.


Description
Product
Last modified on Sep 27, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.