-
Type:
Suggestion
-
Resolution: Unresolved
-
None
-
Component/s: User Management - LDAP Integration
-
None
Issue Summary
As a support engineer, it would be helpful to see the Invocation ID logged every time Jira starts to perform a Full Synchronization against the connected Active Directory User Directories.
Currently, we only track the invocation ID during an Incremental Sync Process
Steps to Reproduce
- Setup Active Directory in Jira as an User Directory
- Verify that Incremental Sync is Disabled
- Save the Configuration and allow Jira to perform a Full Synchronization
Expected Results
In the atlassian-jira.log we want to see the Invocation ID in the log entry like we see when an Incremental Sync is performed
This is an example of what is logged when Jira completes an Incremental Sync with Microsoft AD
Caesium-1-4 INFO ServiceRunner [c.a.c.d.synchronisation.cache.UsnChangedCacheRefresher] Last incremental synchronization took place for AD instance with invocation id '8f4a5b27-3c91-4d28-b0e6-29f4c8a7d3e1', current instance has invocation id of 'c1e92d54-7a63-43bf-9f0a-8142b6c3f907', falling back to full
Actual Results
This data is not stored in the atlassian-jira.log file
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available