[Date Prev][Date Next]
Re: (ITS#8163) Broken handling of deprecated attributes
First, the issue tracker is not for usage questions. Please redirect
your question to openldap-technical mailing list.
On 2015-06-03 10:47, email@example.com wrote:
> Unfortunately, javaRemoteLocation isn't in java.schema and appears to
> 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: conn=1177 op=2 SEARCH RESULT
> err=65 nentries=0 text=
> According to Jira support, this is an incorrect behavior from OpenLDAP,
> matching the LDAP RFCs. Quoting them: "OpenLDAP should not be returning
> an error
> when querying for javaRemoteLocation, even if it is deprecated."
I can confirm that OpenLDAP works correctly in this regard.
You did not post the accompanying SEARCH log line with filter and scope.
You should check that.