My Oracle Support Banner

ODSEE - How to Troubleshoot When the NativeLDAP "cn=proxyagent" User Password is Expired (Doc ID 1231385.1)

Last updated on SEPTEMBER 28, 2020

Applies to:

Oracle Directory Server Enterprise Edition - Version 5.1 and later
Information in this document applies to any platform.

Purpose

Users are not able to login to their systems that are configured as LDAP clients in Native LDAP (Naming Services) configuration.
In the access log file, err=49 for the BIND operation:

[16/Sep/2010:20:52:12 -0600] conn=xxxxx op=0 msgId=1 - BIND dn="cn=proxyagent,ou=profile,<SUFFIX_DN>" method=128 version=3
[16/Sep/2010:20:52:12 -0600] conn=627771 op=-1 msgId=-1 - closed.
[16/Sep/2010:20:52:12 -0600] conn=xxxxx op=0 msgId=1 - RESULT err=49 tag=97 nentries=0 etime=0, password expired!
[16/Sep/2010:20:52:12 -0600] conn=xxxxx op=1 msgId=2 - UNBIND 

***NOTE***  For Solaris NativeLDAP the username "cn=proxyagent" is a hard-coded value.

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Troubleshooting Steps
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.