-
Bug
-
Resolution: Answered
-
High
-
None
-
4.3 - EAP, 4.3
-
None
-
4.03
-
When setting up a directory in JIRA 4.3, if the BaseDN does not contain an Organizational Unit (OU), users cannot log in JIRA. However, the Test Connection is successful. The message "Sorry, an error occurred trying to log you in - please try again." is displayed to the user on the log in screen.
Example:
Works
BaseDN: ou=office,dc=mycompany,dc=com
Does not Work
BaseDN:dc=mycompany,dc=com
Message on the log files when it does not work:
2011-03-16 14:59:06,599 QuartzWorker-0 INFO ServiceRunner [atlassian.crowd.directory.DbCachingRemoteDirectory] synchronisation complete in [ 26ms ] 2011-03-16 14:59:06,648 QuartzWorker-0 ERROR ServiceRunner [atlassian.crowd.directory.DbCachingDirectoryPoller] Error occurred while refreshing the cache for directory [ 10000 ]. com.atlassian.crowd.exception.OperationFailedException: java.util.concurrent.ExecutionException: com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.PartialResultException: nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: mycompany.com:389 [Root exception is java.net.UnknownHostException: mycompany.com]] at com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher.synchroniseAllUsers(UsnChangedCacheRefresher.java:255) at com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseAll(AbstractCacheRefresher.java:34) ... Caused by: java.util.concurrent.ExecutionException: com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.PartialResultException: nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: mycompany.com:389 [Root exception is java.net.UnknownHostException: mycompany.com]] at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher.synchroniseAllUsers(UsnChangedCacheRefresher.java:237) ... 10 more Caused by: com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.PartialResultException: nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: mycompany.com:389 [Root exception is java.net.UnknownHostException: mycompany.com]] at com.atlassian.crowd.directory.SpringLDAPConnector.pageSearchResults(SpringLDAPConnector.java:352) at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntitiesWithRequestControls(SpringLDAPConnector.java:386) ... Caused by: org.springframework.ldap.PartialResultException: nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: mycompany.com:389 [Root exception is java.net.UnknownHostException: mycompany.com]] at org.springframework.ldap.support.LdapUtils.convertLdapException(LdapUtils.java:203) at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:315) ... Caused by: javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: mycompany.com:389 [Root exception is java.net.UnknownHostException: mycompany.com]] at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImpl(LdapNamingEnumeration.java:224) at com.sun.jndi.ldap.LdapNamingEnumeration.hasMore(LdapNamingEnumeration.java:171) at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:295) ... 13 more Caused by: javax.naming.CommunicationException: mycompany.com:389 [Root exception is java.net.UnknownHostException: mycompany.com] at com.sun.jndi.ldap.LdapReferralContext.<init>(LdapReferralContext.java:74) at com.sun.jndi.ldap.LdapReferralException.getReferralContext(LdapReferralException.java:132) at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreReferrals(LdapNamingEnumeration.java:339) at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImpl(LdapNamingEnumeration.java:208) ... 15 more Caused by: java.net.UnknownHostException: mycompany.com at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432)
- is duplicated by
-
CONFSERVER-22066 Disable follow referrals setting when upgrading LDAP configurations to 3.5
- Closed
- is superseded by
-
JRASERVER-24918 'Test Settings' in User management needs perform more complete connection validation
- Closed
-
JRASERVER-24946 Link LDAP integration errors to a cac page helping customers to troubleshoot integration issues
- Closed
- relates to
-
JRASERVER-24140 Improve logging when Active Directory DNS is misconfigured and referrals can't be followed
- Closed