Hi,
Authentication in my application is done at Sun One directory server. Earlier I had 5.1 version...Now when I upgraded it to 5.2, it is throwing [LDAP error 32: No such Object]. Do I need to do any changes in setting the environment? If so, what are the changes to be made, to be compatible with newer version of LDAP. Please any help on this issue is appreciated...
Thanks in advance
Gopal
Sun Java Enterprise System Support Forum and the Directory Server's "Release Notes" [See docs.sun.com] is a good place to find this information. Also upgrade to the latest DS5.2 Patch 4.
One probable cause could be that either the BindDN or the SearchBase used by your application no longer exists in the upgraded server's setup. Please check the access log on the Directory server to pinpoint the culprit. The corresponding entry will have "err=32".
Examples:
SRCH base="dc=abc,dc=example,dc=com" ....
RESULT err=32 tag=101 nentries=0 etime=0
[Note: Tag 101 means the search base does not exist]
BIND dn="cn=user,dc=abc,dc=example,dc=com" ....
RESULT err=32 tag=97 nentries=0 etime=0
[Note: Tag 97 means BindDN does not exist]
Based on your requirements, you will either have to add the missing entry or upgrade your applications' configuration to use an alternative entry.
For more on Access Log contents see
<a href="http://docs.sun.com/source/817-7616/fileref.html#wp20452" target="_blank">http://docs.sun.com/source/817-7616/fileref.html#wp20452< /a>
You should provide more details.
- how did you perform the upgrade? did you read the release notes? did you also migrate customized schema if there is any?
- how do you know the upgrade is successful?
- where/how does the error gets generated?
Gary
