Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-2478

LDAP Delegate: Synchronize with AD to disable deleted users


    • 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.


      Atlassian Update - 21 February 2018

      Hi everyone,

      Thanks for all your votes and comments on this suggestion. Your voice means a lot to us.

      We're excited to announce that we've shipped an experimental plugin (Atlassian Labs) for Crowd that is able to do delegated directory user pruning.

      This plugin allows to optimize your license usage by periodically cleaning inactive users from your delegated directories. After configuring pruning for a delegated directory the plugin will periodically check if the directory contains any users who have been deactivated or removed from the remote directory.

      By default such users will be deactivated in Crowd. It is also possible to enable "hard delete" mode, in which users who have been deleted in the remote directory will also be deleted in Crowd.

      This plugin can be downloaded from Atlassian Marketplace here.


      Atlassian Crowd Team


      When a user is being deleted in the AD, it will not be able to login to Crowd's Applications anymore.
      But as the user still exisits in the LDAP Delegate, it will count against the license limits (of Crowd, Confluence, JIRA, whatever).
      Support (CWDSUP-4973) told me to deactivate the user in Crowd manually in such cases.
      This leads to a double maintenance (delete in AD, deactivate in Crowd). In addition the AD admins might not be Crowd admins.

      Crowd could regularly (once per day?) check if the users in their Delegate Directories are still present/active in the AD and then deactivate them if they are not.

        1. image-2017-10-17-15-55-45-636.png
          160 kB
        2. image-2017-10-17-16-09-03-898.png
          45 kB
        3. image-2017-10-24-11-51-30-128.png
          65 kB
        4. image-2017-10-24-11-53-04-065.png
          68 kB
        5. image-2017-10-24-11-55-35-379.png
          74 kB
        6. image-2018-04-02-23-49-21-541.png
          193 kB
        7. image-2018-04-02-23-51-01-740.png
          233 kB
        8. image-2018-04-03-00-13-56-512.png
          241 kB
        9. screenshot-1.png
          241 kB

            Unassigned Unassigned
            48ff0be30bda Stephan Haslinger
            75 Vote for this issue
            46 Start watching this issue