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.

+++ This bug was initially created as a clone of Bug #876262 +++

Description of problem:
Currently winbind checks is a username returned by getpwnam() contains the winbind separator character if the name used as an argument for getpwnam() contains it.

This will fail with new sssd versions because sssd accepts different styles of fully qualified user names, e.g. user and DOM\user, at the same time but returns only a canonical version.


Version-Release number of selected component (if applicable):
samba-3.6.9-144.el6

How reproducible:

Steps to Reproduce:
1.Install samba on an AD client with sssd but not winbind.
2.Try to access the samba server authenticated. 
3.
  
Actual results:
Using a user name with the winbind seperator char does not work while e.g user works.

Expected results:
All types of sully qualified user names work.

Additional info:
Patch already uptream.

How to setup sssd to connect to the AD. Use realmd?
Also how to access a username with a winbind separator

Please add steps to verify this.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.