Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-65984

Add logging for individual users while performing LDAP synchronization

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • None
    • 0
    • 1
    • Hide
      Atlassian Update – 15 November 2018

      Hi,

      Thank you for providing input and feedback on this suggestion. We have reviewed it and wanted to let you know that requested functionality is available in Crowd 3.2 or newer.

      For those of you who aren’t familiar with Crowd, it offers one place to manage your users, groups and directories and easily integrate your identity infrastructure across all self-hosted Atlassian products.

      In Crowd 3.2 or higher audit log admin can see entries for each event performed during synchronisation like user created, user updated, user added to group, etc.

      We are not planning to invest in similar capabilities in Jira Server in any foreseeable future and we encourage you to consider using Crowd or Crowd Data Center for most efficient user management across your self-hosted Atlassian products.

      Best regards,

      Gosia Kowalska, Jira Server Product Manager

      Show
      Atlassian Update – 15 November 2018 Hi, Thank you for providing input and feedback on this suggestion. We have reviewed it and wanted to let you know that requested functionality is available in  Crowd 3.2  or newer. For those of you who aren’t familiar with  Crowd , it offers one place to manage your users, groups and directories and easily integrate your identity infrastructure across all self-hosted Atlassian products. In  Crowd 3.2  or higher audit log admin can see entries for each event performed during synchronisation like user created, user updated, user added to group, etc. We are not planning to invest in similar capabilities in Jira Server in any foreseeable future and we encourage you to consider using Crowd or Crowd Data Center for most efficient user management across your self-hosted Atlassian products. Best regards, Gosia Kowalska, Jira Server Product Manager
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      Currently, when user perform full synchronization, the events like users added or removed will be "grouped" together like what's shown below:

      017-09-08 17:32:16,800 Caesium-1-2 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteDirectory] INCREMENTAL synchronisation for directory [ 10100 ] starting
2017-09-08 17:32:16,801 Caesium-1-2 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteDirectory] Attempting INCREMENTAL synchronisation for directory [ 10100 ]
2017-09-08 17:32:16,801 Caesium-1-2 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteDirectory] Incremental synchronisation for directory [ 10100 ] was not completed, falling back to a full synchronisation
2017-09-08 17:32:16,801 Caesium-1-2 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteDirectory] INCREMENTAL synchronisation for directory [ 10100 ] was not successful, attempting FULL
2017-09-08 17:32:17,016 Caesium-1-2 INFO ServiceRunner     [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 651 ] remote users in [ 215 ms ]
2017-09-08 17:32:17,061 Caesium-1-2 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 651 ] users for delete in DB cache in [ 44ms ]
2017-09-08 17:32:17,061 Caesium-1-2 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteChangeOperations] scanned for deleted users in [ 44ms ]
2017-09-08 17:32:17,106 Caesium-1-2 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteChangeOperations] scanning [ 651 ] users to add or update
2017-09-08 17:32:17,136 Caesium-1-2 INFO ServiceRunner     [c.a.crowd.directory.DirectoryCacheImplUsingChangeOperations] scanned and compared [ 651 ] users for update in DB cache in [ 75ms ]
2017-09-08 17:32:17,137 Caesium-1-2 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteChangeOperations] adding [ 2 ] users
2017-09-08 17:32:17,145 Caesium-1-2 WARN ServiceRunner     [c.a.crowd.directory.DbCachingRemoteChangeOperations] Could not add the following entity to the directory [ Crowd Internal Directory ]: john
2017-09-08 17:32:17,145 Caesium-1-2 WARN ServiceRunner     [c.a.crowd.directory.DbCachingRemoteChangeOperations] Could not add the following entity to the directory [ Crowd Internal Directory ]: charles
2017-09-08 17:32:17,145 Caesium-1-2 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteChangeOperations] added [ 0 ] users successfully in [ 8ms ]
2017-09-08 17:32:17,146 Caesium-1-2 INFO ServiceRunner     [c.a.crowd.directory.DirectoryCacheImplUsingChangeOperations] synchronised [ 651 ] users in [ 85ms ]
2017-09-08 17:32:17,155 Caesium-1-2 INFO ServiceRunner     [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 30 ] remote groups in [ 9 ms ]
2017-09-08 17:32:17,155 Caesium-1-2 WARN ServiceRunner     [c.a.crowd.model.DirectoryEntities] entity [jira-software-users] of type LDAPGroupWithAttributes duplicated in remote directory. Ignoring all occurrences.
2017-09-08 17:32:17,156 Caesium-1-2 WARN ServiceRunner     [c.a.crowd.model.DirectoryEntities] entity [jira-users] of type LDAPGroupWithAttributes duplicated in remote directory. Ignoring all occurrences.
2017-09-08 17:32:17,163 Caesium-1-2 WARN ServiceRunner     [c.a.crowd.model.DirectoryEntities] entity [jira-administrators] of type LDAPGroupWithAttrib

      Some users would like ability to view individual entries to specific users where changes are performed during synchronization. For example, if an user is disabled during synchronization, user would like to see this from log.

      Suggested Solution

      1. Add function in Audit Log to view newly added or disabled users.
      2. Add new logging so user can view changes for individual users from JIRA' log.

      Workaround

      None

              Unassigned Unassigned
              vshanmugam Vicknesh Shanmugam (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: