problem with incorrect documentation on LDAP Naming Service

Problem with the RTFM

recently I try to help a customer on a problem on LDAP and kerberos integration problem

In the process, we try to setup Native LDAP as Name Service (Solaris 9). After we run the idsconfig to setup the server by following the document on the, it all seems fine.

When we try to use ldapclient to configure the client, our problem started all the example on the client setup are incorrect, we finally need to follow the man page on ldapclient (if we ASSUME that it is correct) and it work?!

May be there is a correct already done by some patches, but we get this document from the current solaris 9 04/04 online document

Using Profiles to initialize a client

ldapclient -p new -d west,

sould be

ldapclient init -a profileName=new

proxy credentials

ldapclient -p profilename -D cn=proxyagent,ou=profile,dc=west,dc=example,dc=com -d -p pitl -w test1234

should be

ldapclient init -a profleName=default -a proxyDN=cn=proxyagent,ou=profile,dc=west,dc=example,dc=com -a proxyPassword=test1234


ldapclient -i -d dc-west, -c dc-west,dc=example,dc=com \ -D cn=proxyagent,ou=profile,dc=west,dc=example,dc=com -w testtest

should be

ldapclient manual -a proxyDn=cn=proxyagent,ou=profile,dc=west,dc=example,dc=com -a proxyPassword=testest

Modifying Manual Client configuration

ldapclient -m -a simple

should be

ldapclient modify -a authenticationMethod=simple

About laotsao 老曹

HopBit GridComputing LLC Rockscluster Gridengine Solaris Zone, Solaris Cluster, OVM SPARC/Ldom Exadata, SPARC SuperCluster
This entry was posted in LDAP. Bookmark the permalink.

One Response to problem with incorrect documentation on LDAP Naming Service

  1. Janos Cserep says:

    We’ve ran into the same problem early this week. The pam.conf example in the Admin guide also didn’t work.
    Although we’ve used auto setup (init), not manual…

Comments are closed.