Bug 810990 - AIX client documentation order clarification.
Summary: AIX client documentation order clarification.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Identity_Management_Guide
Version: 6.3
Hardware: All
OS: All
unspecified
medium
Target Milestone: rc
: 6.3
Assignee: Deon Ballard
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On: 810987
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-09 19:47 UTC by Dmitri Pal
Modified: 2012-06-21 23:16 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 810987
Environment:
Last Closed: 2012-06-21 23:16:22 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Dmitri Pal 2012-04-09 19:47:42 UTC
+++ This bug was initially created as a clone of Bug #810987 +++

Description of problem:

Step 3 of the AIX client installation documentation states:

"Configure the LDAP client settings to use the IPA directory services:
# mksecldap -c -h ipaserver.example.com -d cn=accounts,dc=example,dc=com -a uid=nss,cn=sysaccounts,cn=etc,dc=example,dc=com -p secret"

However, this user is not created on the ipa server until step 11 h:

"On the IPA server, add a user that is only used for authentication. (This can be substituted with krb5 authentication if that works from the LDAP client). Otherwise go to the IPA server and use ldapmodify, bind as Directory Manager and create this user. The user should be assigned a shared password.
ldapmodify -D "cn=directory manager" -w secret -p 389 -h ipaserver.example.com -x -a

dn: uid=nss,cn=sysaccounts,cn=etc,dc=example,dc=com
objectClass: account
objectClass: simplesecurityobject
objectClass: top
uid: nss
userPassword: secretpassword"

If a user follows these instructions in this order then the mksecldap command will fail.

Step 11 h should be moved to step 3 a, and the existing step 3 should be moved to step 3 b.

Comment 5 Deon Ballard 2012-06-21 23:16:22 UTC
Closing.


Note You need to log in before you can comment on or make changes to this bug.