Hide Forgot
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
Samba/net bug for invalid principals in the keytab is https://bugzilla.redhat.com/show_bug.cgi?id=749142.
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.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.