Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1450107
Description of problem: If short username resolution is enabled in the config file for a trusted domain: [domain/main_domain/trusted_domain] use_fully_qualified_names = False then sssd always returns a shortname. But, the shortname, when used as an input, always routes into the main_domain. This leads to a schizophrenic situation, where login through some PAM applications like su first runs getpwnam, receives the UID and primary GID of the user from trusted domain, but the rest of the PAM conversation, including checking the credentials is done against the parent domain. Version-Release number of selected component (if applicable): sssd-1.15.2-29.el7 How reproducible: always Steps to Reproduce: 1. join sssd to an AD forest with multiple domains 2. configure one of the trusted domains to use shortnames only 3. run: "su - user@trusted_domain" 4. enter credentials of user@main_domain Actual results: you're logged in Expected results: you should be denied access Additional info:
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1450107
Metadata Update from @fidencio: - Issue assigned to fidencio
PR opened: https://github.com/SSSD/sssd/pull/311
Metadata Update from @fidencio: - Custom field patch adjusted to on - Issue set to the milestone: None
Metadata Update from @jhrozek: - Issue close_status updated to: Fixed - Issue set to the milestone: SSSD 1.15.3 - Issue status updated to: Closed (was: Open)
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/4430
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.