Bug 2229011

Summary: force user/group breaks samba
Product: Red Hat Enterprise Linux 8 Reporter: Eugene Keck <ekeck>
Component: sambaAssignee: Andreas Schneider <asn>
Status: CLOSED MIGRATED QA Contact: sssd-qe
Severity: high Docs Contact:
Priority: high    
Version: 8.6CC: asn, dkarpele, pfilipen
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-04 09:21:04 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:

Comment 1 Andreas Schneider 2023-08-17 08:02:20 UTC
[2023/07/27 12:31:43.434346,  3, pid=1019460, effective(0, 0), real(0, 0)] ../../source3/lib/util_names.c:84(is_allowed_domain)
  is_allowed_domain: Not trusted domain 'UNIX USER'
[2023/07/27 12:31:43.434350,  3, pid=1019460, effective(0, 0), real(0, 0), class=auth] ../../source3/auth/auth_util.c:492(create_local_token)
  create_local_token: Authentication failed for user [cortexuser] from firewalled domain [UNIX USER]


grep allow etc/samba/smb.conf       
17:        allow trusted domains = no


This prevents the force user to be working ...

Comment 2 Andreas Schneider 2023-09-04 09:14:09 UTC
Workaround:

Use `winbind:ignore domains` smb.conf option instead of `allow trusted domains = no`


Upstream discussion if this is a bug:

https://lists.samba.org/archive/samba-technical/2023-September/138398.html

Comment 3 RHEL Program Management 2023-09-04 09:17:11 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 4 RHEL Program Management 2023-09-04 09:21:04 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.