I have used realmd to join a host to an Active Directory domain. Realmd uses sssd-ad for this, which pulls in sssd-krb5-common but _not_ sssd-krb5. Unfortunately, sssd-krb5-common does not install the snippet /etc/krb5.conf.d/enable_sssd_conf_dir. This results in SSH refusing gssapi-with-mic authentication. When I additionally install the sssd-krb5 package (which includes the snippet), or create the snippet manually, SSH logins use my SSSD config and GSSAPI authentication goes through. Reproducible: Always Steps to Reproduce: 1. Install realmd on a host 2. Join host to Active Directory domain 3. Enable SSH daemon 4. ssh -l user@realm -o preferredauthentications=gssapi-with-mic host Actual Results: Authentication is denied, no SSH session opened Expected Results: Authentication goes through, SSH session is opened
Hi, thank you for making us aware of this issue. Alexey, what do you think? bye, Sumit
(In reply to Sumit Bose from comment #1) > Hi, > > thank you for making us aware of this issue. > > Alexey, what do you think? Imo, makes sense.
Upstream PR: https://github.com/SSSD/sssd/pull/7875
Pushed PR: https://github.com/SSSD/sssd/pull/7875 * `master` * 764798d7ac0c3cdd879a76047e065db6f21c9901 - SPEC: package 'enable_sssd_conf_dir' as a part of 'sssd-krb5-common'
This message is a reminder that Fedora Linux 41 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '41'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 41 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.