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.
Cause: The LDAP provider manual page stated that GSSAPI authentication is used and the Kerberos realm is not specified, the
system default would be used. However, the LDAP provider code did not fall back to the system default Kerberos realm when
the realm was not specified in the config file.
Consequence: The documentation did not match the code
Fix: The LDAP provider was fixed so that it is able to fall back to the default realm configured in /etc/krb5.conf
Result: The documentation matches the code
Description of problem:
The sssd-ldap manual page says:
krb5_realm (string)
Specify the Kerberos REALM (for SASL/GSSAPI auth).
Default: System defaults, see /etc/krb5.conf
That's not true since we added the online/offline callbacks to create and delete kdcinfo files. They require the realm to be specified to construct the pathname of the kdcinfo files.
If the realm is not specified, the provider does not even start and quits with a rather confusing error message (the code strdups the NULL realm and thinks it hits an OOM situation).
Version-Release number of selected component (if applicable):
sssd-1.5.1-47.el6
Steps to Reproduce:
1. configure an LDAP provider with GSSAPI authentication and omit the krb5_realm option
2. start sssd
Actual results:
the provider does not start
Expected results:
the provider should start
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause: The LDAP provider manual page stated that GSSAPI authentication is used and the Kerberos realm is not specified, the
system default would be used. However, the LDAP provider code did not fall back to the system default Kerberos realm when
the realm was not specified in the config file.
Consequence: The documentation did not match the code
Fix: The LDAP provider was fixed so that it is able to fall back to the default realm configured in /etc/krb5.conf
Result: The documentation matches the code
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-2011-1529.html
Description of problem: The sssd-ldap manual page says: krb5_realm (string) Specify the Kerberos REALM (for SASL/GSSAPI auth). Default: System defaults, see /etc/krb5.conf That's not true since we added the online/offline callbacks to create and delete kdcinfo files. They require the realm to be specified to construct the pathname of the kdcinfo files. If the realm is not specified, the provider does not even start and quits with a rather confusing error message (the code strdups the NULL realm and thinks it hits an OOM situation). Version-Release number of selected component (if applicable): sssd-1.5.1-47.el6 Steps to Reproduce: 1. configure an LDAP provider with GSSAPI authentication and omit the krb5_realm option 2. start sssd Actual results: the provider does not start Expected results: the provider should start