#3259 SSH: default_domain_suffix is not being used for users' authorized keys
Closed: Fixed Opened by jhrozek.

In commit eeecc48 we disabled
default_domain_suffix for the SSH responder, but in a wrong way -- we
disabled the functionality completely, also for users, not only for
computers. This might have been correct at the time, since SSH keys in ID
overrides are a relatively new feature, but it's definitely not correct
in general.

Instead, this patch restores the use of default_domain_suffix, but only
for looking up public keys of users, not of groups.


Fields changed

owner: somebody => jhrozek
status: new => assigned

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1401816 (Red Hat Enterprise Linux 7)

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=1401816 1401816]

  • master: ed71fba97dfcf5b3f0f1834c06660c481b9ab3ce
  • sssd-1-14: 2949fe58ac344c44d756ca309d4b2b7f3590cee3

resolution: => fixed
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: NEEDS_TRIAGE

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4292

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata