-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
5.0.6, 5.2.5
-
5
-
12
-
Severity 2 - Major
-
4
-
We need to improve how we handle duplicate groups. Right now we just throw an error and fail. This results in support tickets. Instead we should have some kind of intuitive error thrown within the JIRA interface which offers a solution / workaround at the minimum. Ideally the logic would present the duplicate groups FQDNs and allow the user to pick which one they want to use.
2012-06-04 12:18:44,664 QuartzWorker-1 ERROR ServiceRunner [atlassian.crowd.directory.DbCachingDirectoryPoller] Error occurred while refreshing the cache for directory [ 10200 ]. com.atlassian.crowd.exception.OperationFailedException: Unable to synchronise directory: duplicate groups with name 'IT' at com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseMemberships(AbstractCacheRefresher.java:131)
- is related to
-
JRASERVER-66599 LDAP group can't be added during login due to duplicate key row
- Gathering Impact
- relates to
-
JRASERVER-67942 Local groups should be applied globally over user directories
- Gathering Interest
(1 mentioned in)