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.
Created attachment 1781991[details]
deployment-script
Created attachment 1781991[details]
deployment-script
# Topology
```
/\ /\
/ \ / \
/ \ / \
/ \ / \
/ \ One way cross forest transitive trust / \
/ \ <----------------------------------------- / \
/EXAMPLE.COM\ /MYDOMAIN.COM\
/______________\ /______________\
\ |
\ |
\ |
\ One way cross forest transitive trust +-----------------------+
/\ <----------------------------------- | RHEL7.9 joined |
/ \ | to the above domain |
/CHILD\ +-----------------------+
/______\
1. RHEL7.9 uses realm join MYDOMAIN.COM
2. And uses adcli join CHILD.EXAMPLE.COM
3. MYDOMAIN.COM has a one way: outgoing trust to EXAMPLE.COM and CHILD.EXAMPLE.COM
```
# Issues
1. I uses following script to add a RHEL7 client to AD
[ad-sssd-rhel7-v2.txt](https://github.com/SSSD/sssd/files/6458299/ad-sssd-rhel7-v2.txt)
2. sssd version is:
```
[root@ip-172-31-7-69 ~]# rpm -qa | grep sssd
python-sssdconfig-1.16.5-10.el7_9.7.noarch
sssd-client-1.16.5-10.el7_9.7.x86_64
sssd-krb5-common-1.16.5-10.el7_9.7.x86_64
sssd-ipa-1.16.5-10.el7_9.7.x86_64
sssd-krb5-1.16.5-10.el7_9.7.x86_64
sssd-proxy-1.16.5-10.el7_9.7.x86_64
sssd-common-1.16.5-10.el7_9.7.x86_64
sssd-common-pac-1.16.5-10.el7_9.7.x86_64
sssd-ad-1.16.5-10.el7_9.7.x86_64
sssd-ldap-1.16.5-10.el7_9.7.x86_64
sssd-1.16.5-10.el7_9.7.x86_64
```
3. user `terry-child` is from domain CHILD.EXAMPLE.COM; `terry-example` is from domain EXAMPLE.COM and `admin` is from domain MYDOMAIN.COM. Only id terry-child and admin can return correct information.
```
[root@ip-172-31-7-69 ~]# id admin
uid=704201113(admin) gid=704200513(domain users) groups=704200513(domain users)
[root@ip-172-31-7-69 ~]# id terry-child
uid=1872601114(terry-child) gid=1872600513(domain users) groups=1872600513(domain users)
```
4. id terry-example will return `no such user` unless I use fully qualified user name
```
[root@ip-172-31-7-69 ~]# id terry-example
id: terry-example: no such user
[root@ip-172-31-7-69 ~]# id terry-example
uid=1952601113(terry-example) gid=1952601113(terry-example) groups=1952601113(terry-example),1952600513(domain users)
```
5. Both uid and gid will be mapped to `terry-example`, but the users from the domain the linux client joined directly will be mapped to terry-child and domain users.
```
[root@ip-172-31-7-69 ~]# ll /home/
total 0
drwx------. 2 terry-child domain users 83 May 11 10:22 terry-child
drwx------. 2 terry-example terry-example 83 May 11 09:07 terry-example
```
# Action Require
1. id/getent passwd shortname of a user from trusted subdomain returns correct information
2. uid and gid should be mapped the shortnames of a user
# sssd logs
[sssd.tar.gz](https://github.com/SSSD/sssd/files/6458827/sssd.tar.gz)