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.
Description of problem:
When joining an AD domain with "net ads join" a keytab /etc/krb5.keytab is being created and a valid Kerberos host principal in the file is HOSTNAME$@REALM (i.e., for host client-123.ad.example.com the principal would be CLIENT-123$@AD.EXAMPLE.COM). SSSD can be configured to use this principal with
ldap_sasl_mech = GSSAPI
ldap_sasl_authid = HOSTNAME$@REALM
Thus local logins using AD for id/auth work fine with SSSD but remote logins won't work since it is not possible to configure the host principal name with sshd.
It should be possible to configure the host principal name with sshd to make it possible to use the Samba provided Kerberos host principal from the host keytab.
Version-Release number of selected component (if applicable):
RHEL 6.2
Comment 3RHEL Program Management
2011-10-30 05:47:21 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
It was discussed over IRC that this might not needed after all, it'd be better to fix the issue with Samba generating such a keytab described in bug 749142.
However, it should be noted that it was suggested in bug 748757 about this same issue with mount.cifs that it would make sense to try the AD style principal of HOSTNAME$@REALM if the host/fqdn@REALM principal does not work.
I'll leave it up to your judgement whether it would make sense to do anything with sshd.
Comment 6RHEL Program Management
2011-12-09 10:05:08 UTC
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.