Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Authconfig should have a UI and CLI option to configure SSSD with IPA back end.
Comment 1Stephen Gallagher
2011-08-17 02:07:46 UTC
It should be noted that this will not be as simple as setting up an LDAP+KRB5 domain is right now.
The proper solution to this ticket will be for authconfig to integrate with the python API provided by the freeipa-client package so that authconfig can be used to join an IPA domain. This entails authenticating as a FreeIPA user with privilege to add new clients, retrieving a keytab and setting up SSSD to use this keytab to connect to the FreeIPA server(s).
Right now, there's a bit of a circular dependency with the freeipa-client, as the 'ipa-client-install' command currently does this work and calls out to authconfig to set up the nsswitch, krb5 and PAM configurations.
So we'll need to coordinate this on both sides of the issue.
There should be a switch/api call flag in the ipa-client-install to not call the authconfig then. Authconfig does not handle calls of itself when its being already running correctly.
A division of labor would need to be very clear. Who writes krb5.conf, sssd.conf, ldap.conf, etc.? Depending on where that line is will help determine the best way in IPA to handle this.
For example, if authconfig is going to write all the config files then we may be able to simplify this a lot and have it call ipa-join directly. If ipa-client-install is still going to write the non nss/pam config files then yes, a switch (perhaps undocumented) would be the way to go.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2012-0931.html