Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-819

Allow account deactivation for unverified accounts

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Use Case

      • Invited a new domain account to Jira, Confluence and Bitbucket cloud, granting license.
      • User did not action the invite and the account remain unused and unverified.
      • On a clean up activity, the unverified account is not available in Managed Accounts and cannot be deactivated to free up licenses. (see ACCESS-617)
      • Product admins would need to revoke access individually on the cloud products to revoke license.

      Suggestion :

      Allow org admins to deactivate unused / unverified accounts or have an alternative option in Managed accounts to revoke license for all products at once.

      Workaround :

      Use User Provisioning to automatically provision active accounts. Deactivation can then be managed from the IDP for freeing up licenses taken by the Atlassian Account.

            [ACCESS-819] Allow account deactivation for unverified accounts

            We have gotten the same exact error as above - is there a plan to resolve this without having to use any workarounds?

            Lumos Yoshikoshi added a comment - We have gotten the same exact error as above - is there a plan to resolve this without having to use any workarounds?

            Srecko Anzic added a comment - - edited

            I followed these instructions https://developer.atlassian.com/cloud/admin/user-management/rest/api-group-users/#api-users-account-id-manage-lifecycle-disable-post , used powershell Invoke-RestMethod and for For verified accounts it worked.
            For unverified accounts I was getting this error message:
            Invoke-RestMethod : {"key":"forbidden.targetUnverified","context":"Error: Cannot perform action on unverified account","errorKey":"forbidden.target-unverified","errorDetail":"Error: Cannot perform action on unverified account"}

            I will just delete those unverified users by using:
            $url = "https://xyz.atlassian.net/rest/api/3/user?accountId=123f-567f-901f"
            $headers = @{"Authorization" = "Basic $encodedCreds"}
            $result = Invoke-RestMethod -Method DELETE -Uri $url -Headers $headers -ContentType "application/json"
             

            Srecko Anzic added a comment - - edited I followed these instructions https://developer.atlassian.com/cloud/admin/user-management/rest/api-group-users/#api-users-account-id-manage-lifecycle-disable-post  , used powershell Invoke-RestMethod and for For verified accounts it worked. For unverified accounts I was getting this error message: Invoke-RestMethod : {"key":"forbidden.targetUnverified","context":"Error: Cannot perform action on unverified account","errorKey":"forbidden.target-unverified","errorDetail":"Error: Cannot perform action on unverified account"} I will just delete those unverified users by using: $url = "https://xyz.atlassian.net/rest/api/3/user?accountId=123f-567f-901f" $headers = @{"Authorization" = "Basic $encodedCreds"} $result = Invoke-RestMethod -Method DELETE -Uri $url -Headers $headers -ContentType "application/json"  

            Rishi Dhar added a comment -

            Looks like its possible to deactivate these using the console but I can't seem to use the Atlassian User Management Rest API to do the same action (deactivate unverified accounts)

            https://developer.atlassian.com/cloud/admin/user-management/rest/intro/

             

            Rishi Dhar added a comment - Looks like its possible to deactivate these using the console but I can't seem to use the Atlassian User Management Rest API to do the same action (deactivate unverified accounts) https://developer.atlassian.com/cloud/admin/user-management/rest/intro/  

            I have accounts created with error in names or mail address, so never activated (due to bad mail address), and it is impossible to deactivate them. They still count but are useless. Thanks to fix this issue.

            Laurent METAIS added a comment - I have accounts created with error in names or mail address, so never activated (due to bad mail address), and it is impossible to deactivate them. They still count but are useless. Thanks to fix this issue.

              Unassigned Unassigned
              rmacalinao Ramon M
              Votes:
              29 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated:
                Resolved: