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 2208273

Summary: user from one-way trusted domains cannot login by using winbind
Product: Red Hat Enterprise Linux 8 Reporter: bobin <bobinjosek>
Component: sambaAssignee: Andreas Schneider <asn>
Status: CLOSED INSUFFICIENT_DATA QA Contact: sssd-qe
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.4CC: aboscatt, asn, dkarpele, pfilipen
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-27 11:53:16 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 bobin 2023-05-18 12:54:36 UTC
Description of problem:
Linux servers (RHEL 8) joined to a local Active Directory (AD) forest/domain (windows server 2019)  using samba-winbind. But logins to the Linux servers failed for users who coming in from a trusted(transitive) AD forest(windows server 2019).If we created one way trust.If we create bi-directoional trust, it's working. But we don't want to go for bi-directorional trust.

Version-Release number of selected component (if applicable):
samba-winbind-4.13.3-11.el8_4.x86_64 (Packages are from RHEL 8.4)

How reproducible:
Yes and reproducible

Steps to Reproduce:
1. install samba-winbind-4.13.3-11.el8_4.x86_64
2. join Linux server (RHEL 8.4) into local Active Directory
3. Clear cache and restart winbind: systemctl stop winbind; net cache flush; rm -f /var/lib/samba/*.tdb; systemctl start winbind
3. do a `id <username>` which returns "no such user" for trusted domain user


Actual results:
Trusted domain/forest user information cannot be retrieved on the Linux servers running samba-winbind-4.13.3-11.el8_4.x86_64. Trusted domain users logins failed.

Expected results:
`id` command can returns user info from trusted domain and we could login with trusted domain users in Linux servers

Additional info:

Comment 1 Andreas Schneider 2023-06-01 08:26:55 UTC
Did just the `id` command fail or did you really try to login as the user? The `id` command might not be able to get information about the user until the user actually has been logged in once ...

Comment 2 Andre Boscatto 2023-06-15 08:20:34 UTC
ping

Comment 3 Red Hat Bugzilla 2023-10-26 04:25:12 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days