Bug 761685

Summary: Doc on setting up a Kerberized NFf Server and Client is not accurate
Product: Red Hat Enterprise Linux 6 Reporter: Steve Dickson <steved>
Component: ipaAssignee: Rob Crittenden <rcritten>
Status: CLOSED DUPLICATE QA Contact: IDM QE LIST <seceng-idm-qe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2CC: mkosek
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-08 20:18:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Steve Dickson 2011-12-08 20:09:05 UTC
Description of problem:
The here are the correction for the following steps:

Chapter 9.3. Setting up a Kerberized NFS Server
 - I removed the 'v4'  

6. Install the NFS package. For example:
    yum install nfs-utils

7. Add the NFS probe modules. 
  - Not needed

9. Edit the NFS server configuration to use NFSv4 security. 
   vi /etc/sysconfig/nfs
   uncomment SECURE_NFS="yes"

10. Edit the NFS common configuration to enable the domain and UID/GID mapping.
    - Not needed.
11. Configure the NFS domain
    - is only needed if clients and servers are in different DNS domains

15. Restart the NFS server.

Changes for: 9.3.2. Setting up a Kerberized NFS Client

5. Edit the NFS common configuration to enable the domain and UID/GID mapping
   - Not needed
6. Edit the NFS common configuration to enable the domain and UID/GID mapping.
   - Definitely not needed.. ;-)

7. Configure the NFS domain. The idmapd.conf must be the same on the NFS client as it is on the NFS server.
   - again only needed if clients and the server are in different DNS domains

8. Start the GSS and name mapping daemons. 
   - only the rpcgssd daemon has to be started.
     service rpcgssd start

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Steve Dickson 2011-12-08 20:18:16 UTC

*** This bug has been marked as a duplicate of bug 761650 ***