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.

Bug 1450107

Summary: SSSD doesn't handle conflicts between users from trusted domains with the same name when shortname user resolution is enabled
Product: Red Hat Enterprise Linux 7 Reporter: Jakub Hrozek <jhrozek>
Component: sssdAssignee: SSSD Maintainers <sssd-maint>
Status: CLOSED ERRATA QA Contact: Dan Lavu <dlavu>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: amaris, dlavu, grajaiya, jhrozek, lslebodn, mkosek, mzidek, pbrezina, sgoveas, tscherf
Target Milestone: rcKeywords: Security
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sssd-1.15.2-49.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 09:06:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jakub Hrozek 2017-05-11 14:30:03 UTC 
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:
Comment 2 Jakub Hrozek 2017-05-22 07:28:48 UTC 
Upstream ticket:
https://pagure.io/SSSD/sssd/issue/3403
Comment 3 Jakub Hrozek 2017-06-21 09:32:53 UTC 
master:
 * fa2fc8a2908619031292eaf375eb1a510b8b2eba
 * 86526891366c4bc3e1ee861143b736d2670a6ba8
Comment 5 Dan Lavu 2017-06-23 15:38:50 UTC 
Verified against sssd-1.15.2-50.el7.x86_64

# Configuration
[sssd]
domains = sssdad.com
config_file_version = 2
services = nss, pam

[domain/sssdad.com]
debug_level = 9
ad_domain = sssdad.com
krb5_realm = SSSDAD.COM
realmd_tags = manages-system joined-with-samba 
cache_credentials = True
id_provider = ad
krb5_store_password_if_offline = True
default_shell = /bin/bash
ldap_sasl_authid = AUTO-HV-01-GUES$
ldap_id_mapping = True
use_fully_qualified_names = False 
fallback_homedir = /home/%u@%d
access_provider = ad

[domain/sssdad.com/child1.sssdad.com]
use_fully_qualified_names = False


# With parent domain user password
[sssdtest@auto-hv-01-guest03 ~]$ su - sssdtest.com
Password: 
su: Authentication failure

# With child domaiin user password, actual user password
[sssdtest@auto-hv-01-guest03 ~]$ su - sssdtest.com
Password: 
Last login: Fri Jun 23 11:29:34 EDT 2017 on pts/0
Last failed login: Fri Jun 23 11:36:17 EDT 2017 on pts/0
There was 1 failed login attempt since the last successful login.
Comment 6 errata-xmlrpc 2017-08-01 09:06:23 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:2294