2018-04-04 12:46:35,818 Caesium-1-1 DEBUG ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] loading remote groups 2018-04-04 12:46:35,818 Caesium-1-1 ERROR ServiceRunner [c.a.c.d.ldap.name.SearchDN] Group Search DN could not be parsed javax.naming.InvalidNameException: Invalid name: IPLDAP
Caused by: org.springframework.ldap.UncategorizedLdapException: Unable to find the groupname of the principal.
Connecting to Novell eDirectory fails
Is there someone who get it working.
Typically this kind of error indicates there is a problem with one or more of the values in the base dn, user dn, and/or group dn that Jira is using to try to make these LDAP requests to. There is a related KB on this problem from our bitbucket space in https://confluence.atlassian.com/bitbucketserverkb/ldap-sync-fails-with-invalidnameexception-808616937.html
I realize this is for Jira and not bitbucket, but the error messages are lining up so closely that I think this is the same problem and in turn it likely has the same source cause. Try following that KB and let us know the results.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events