« December 2009
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
  
       
Today

Blog::Navigation

Blog::Editing

Bookmarks::Blogroll

Blog::Referrers

Today's Page Hits: 746

Site notes

This page validates as XHTML 1.0, and will look much better in a browser that supports web standards, but it is accessible to any browser or Internet device. It was created using techniques detailed at glish.com/css/.

Powered by Roller Weblogger.
« Manual Failover... | Main | Building customer... »
Thursday Jun 10, 2004

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 http://docs.sun.com, 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,example.com 192.168.0.0

sould be

ldapclient init -a profileName=new 192.168.0.1

proxy credentials

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

should be

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

Manually

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

should be

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

Modifying Manual Client configuration

ldapclient -m -a simple

should be

ldapclient modify -a authenticationMethod=simple

Comments:

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...

Posted by Janos Cserep on June 10, 2004 at 01:59 PM EDT #

Post a Comment:
Comments are closed for this entry.
Copyright (C) 2003, hstsao