RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 692607 - rhel6 ipa doc - change references of freeipa into ipa
Summary: rhel6 ipa doc - change references of freeipa into ipa
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Identity_Management_Guide
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Deon Ballard
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: 646217
TreeView+ depends on / blocked
 
Reported: 2011-03-31 17:01 UTC by Marc Sauton
Modified: 2011-06-16 02:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-16 02:03:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Marc Sauton 2011-03-31 17:01:14 UTC
Description of problem:

there are references of the upstream version into the Enterprise Identity Management Guide
example with
yum install freeipa-server
on RHEL 6.x it should be
yum install ipa-server


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

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/96/html/Enterprise_Identity_Management_Guide/chap-Enterprise_Identity_Management_Guide-Installing_the_IPA_Server.html


How reproducible:


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


Expected results:


Additional info:

Comment 2 Marc Sauton 2011-03-31 18:35:34 UTC
more notes and suggestions for

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/96/html-single/Enterprise_Identity_Management_Guide/index.html


**********
5.7. DNS
...
You can use the domain name example.com and the realm FREEIPA.

==>
suggestion:
You can use the domain name example.com and the realm TESTIPA.


**********
6.1. Installing the IPA Server Packages
yum install freeipa-server
yum install freeipa-server bind bind-dyndb-ldap

==>
should be:
yum install ipa-server
yum install ipa-server bind bind-dyndb-ldap


**********
Procedure 8.3. To download and install the Fedora IPA packages and dependencies:

==>
Procedure 8.3. To download and install the IPA packages and dependencies:

**********

#
Install the appropriate IPA client packages:
For a user workstation, run the following command:
# yum install freeipa-client
For an administrator workstation, run the following command:
# yum install freeipa-client freeipa-admintools 

==>
yum install ipa-client
yum install ipa-client ipa-admintools


**********
22.1.4.2.1. Configuration Options
...
This is the same configuration as that provided for freeIPA v1.x 

==>
This is the same configuration as that provided for IPA v1.x 


**********
in:

1.1. Operating System Requirements
The main assumption here is that you have a computer installed with either a Red Hat Enterprise Linux or Fedora operating system (OS). While these examples were written based on Fedora 14, the concepts, procedures, and commands are the same for both OSes.

==>
Do we really need this last sentence?
If this is for an Enterprise Identify Management Guide, I would propose to remove it.


**********
in:

2.1. Determining Which Version to Install

==>
why do we suggest to install the upstream version using a personal Fedora account and personal yum repo?
If this is for an Enterprise Identify Management Guide, I would propose to remove this section, we should suggest the usage of RHN.


**********
in:

8.2.5. Configuring NFS v4 with Kerberos
Procedure 8.4. To configure NFS on the Fedora IPA client:

==>
If this is for an Enterprise Identify Management Guide, I would propose to provide an example using a RHEL client, not upstream ones.

Comment 3 David O'Brien 2011-03-31 22:31:33 UTC
Looks like it got built with a missing condition. Everywhere else "freeipa" -> "ipa" when referring to RHEL

wrt 2.1. Determining Which Version to Install

I think Dmitri's idea here was to provide alternatives; if you want to use the version of IPA provided with the OS release, that's fine, but you might not have all the latest devel bits, etc. (bearing in mind that for 6.1 IPA is still Tech Preview). If you want to get the latest bits and therefore a sneak preview of what's coming, you'll need to use devel repos.

Dmitri?

wrt 8.2.5. Configuring NFS v4 with Kerberos
Procedure 8.4. To configure NFS on the Fedora IPA client:


Both procedures are provided. There are currently separate sections for installing & configuring Fedora and RHEL clients. The long term plan is to combine these, but first I wanted to ensure that there were few, if any, differences (e.g., for IPAv1 we had separate and incompatible install scripts for RHEL4 & RHEL5). There was no time for this in the 6.1 time frame.

The other mods you mention are trivial and will only take a few minutes.

Thanks for the review.

Comment 4 Dmitri Pal 2011-04-06 20:11:12 UTC
(In reply to comment #3)
> Looks like it got built with a missing condition. Everywhere else "freeipa" ->
> "ipa" when referring to RHEL
> 
> wrt 2.1. Determining Which Version to Install
> 
> I think Dmitri's idea here was to provide alternatives; if you want to use the
> version of IPA provided with the OS release, that's fine, but you might not
> have all the latest devel bits, etc. (bearing in mind that for 6.1 IPA is still
> Tech Preview). If you want to get the latest bits and therefore a sneak preview
> of what's coming, you'll need to use devel repos.
> 
> Dmitri?

Yes.

If you are on RHEL you just install the version that is on RHEL and you do not need this section at all.
On fedora you might install the one that comes from Fedora or a version from upstream from the devel repo if you want the latest bits.
In some cases in the middle of Fedora release cycle there might be a stable upstream version that is better than the one available from Fedora. One can install that version but this release would most likely appear in the core Fedora in couple weeks after it has been released upstream. 


> 
> wrt 8.2.5. Configuring NFS v4 with Kerberos
> Procedure 8.4. To configure NFS on the Fedora IPA client:
> 
> 
> Both procedures are provided. There are currently separate sections for
> installing & configuring Fedora and RHEL clients. The long term plan is to
> combine these, but first I wanted to ensure that there were few, if any,
> differences (e.g., for IPAv1 we had separate and incompatible install scripts
> for RHEL4 & RHEL5). There was no time for this in the 6.1 time frame.
> 

Nothing changed regarding setup of of RHEL4. It needs to be configured manually using nss_ldap in nsswitch.conf and pam config files.

On RHEL 5 there is an ipa-client script.
In 5.6 it configures nss_ldap and pam_krb5. 
In later versions (5.7) the SSSD with native IPA back end (not generic LDAP + Kerberos back ends) will be used.
 


> The other mods you mention are trivial and will only take a few minutes.
> 
> Thanks for the review.

Comment 5 David O'Brien 2011-04-07 00:56:03 UTC
ok, I conditionalised that section to be fedora-specific. For the Enterprise doc it doesn't appear at all.

I don't discuss IPA configuration of IPA for RHEL 4 at all. It was not included in the list of supported clients for IPA 2.0.

Setting to MODIFIED.

Will brew and push when I can.

Comment 6 David O'Brien 2011-04-08 03:34:02 UTC
Red_Hat_Enterprise_Linux-Enterprise_Identity_Management_Guide-96-web-en-US-0.7-30.el5

You shouldn't see any references to devel repos, etc., in the Enterprise edition now.

Neither should there be any references to "freeipa-server" packages. For RHEL, the packages are "ipa-server" (and "ipa-client", etc.)


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