[Date Prev][Date Next] [Chronological] [Thread] [Top]

(ITS#8163) Broken handling of deprecated attributes

Full_Name: Pierre Schweitzer
Version: 2.4.40
OS: Ubuntu LTS 12.04.5
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (


We are currently facing an issue with Jira 6.0.8 while interfacing it with
OpenLDAP. When loging in, Jira attempts to query the following attributes:
"uid mail sn givenName displayName objectClass javaSerializedData javaClassName
javaFactory javaCodeBase javaReferenceAddress javaClassNames
Unfortunately, javaRemoteLocation isn't in java.schema and appears to be

OpenLDAP replies with (ldapsearch result):
# search result
search: 2
result: 65 Object class viatation
Seen from OpenLDAP logs:
Apr 22 13:09:27 rose-java slapd[25272]: conn=1177 op=2 SEARCH RESULT tag=101
err=65 nentries=0 text=

According to Jira support, this is an incorrect behavior from OpenLDAP, not
matching the LDAP RFCs. Quoting them: "OpenLDAP should not be returning an error
when querying for javaRemoteLocation, even if it is deprecated."

If required for testing, we can provide more details such as Jira queries.