Configuring LDAP Results in 'Unprocessed Continuation References'
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Content of this KB page relates to system running JIRA prior to the 4.3 release.
Symptoms
The following appears in the atlassian-jira.log:
1
2
3
4
5
2008-02-20 08:35:07,143 http-443-Processor21 ERROR [user.provider.ldap.LDAPCredentialsProvider] Connected but encountered error checking if LDAP had more results. For Unprocessed Continuation References, try adding <property name="java.naming.referral">follow</property> to the LDAPCredentialsProvider config.
javax.naming.PartialResultException: Unprocessed Continuation Reference(s); remaining name 'dc=mcdonaldbradley,dc=local'
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2784)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2758)
at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1812)
Cause
JIRA matches more than one result in your LDAP server and it is trying to search to another domain but cannot.
Resolution
Add the following property in <install directory>atlassian-jira/WEB-INF/classes/osuser.xml:
1
<property name="java.naming.referral">follow</property>
ℹ️Please see our Troubleshooting LDAP User Management documentation for further assistance with diagnosing LDAP problems.
Was this helpful?