#3221 RFE: Make "sssd-libwbclient" to display real names in permission dialog
Opened 2 years ago by lslebodn. Modified a year ago

Ticket was cloned from Red Hat Bugzilla (product Fedora): Bug 1323771

Created attachment 1143388
smb.conf file

Description of problem:

This may not be a bug or may not be a bug it just maybe that I don't understand
the configuration I need to make "sssd-libwbclient" work. Maybe the bug would
then be lack of documentation?

It's my understanding that if using SSSD joined machine to AD you should have
to use Winbind anymore but can use sssd-libwbclient to do SID<->UID mapping.
All I should have to do is run:

# alternatives --set libwbclient.so.0.12-64

Verify with

# alternatives --display libwbclient.so.0.12-64
libwbclient.so.0.12-64 - status is manual.
 link currently points to /usr/lib64/sssd/modules/libwbclient.so.0.12.0

Then you don't need anything specifically in smb.conf for mapping or do you
still need to specify winbind options?

I have attached my smb.conf.

When I go to the properties of a directory in the test share on this machine
from Windows and select the security tab, I just see the SID's and not the
names of the domain users. Though these SID's seem to be valid entries for the

Also if I add permission entries from Windows it works when I add new entries
by name using domain accounts. These successfully add and the permissions get
added correctly to the directory but if I reopen the dialog, these new entries
are just SID's as well as the existing ones.

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
1. Have an AD joined SSSD machine.

2. Switch Samba to use ssd-libwbclient for SID mapping by running
 alternatives --set libwbclient.so.0.12-64

3. Browse to a share and select properties and the security tab

Actual results:
Displays items as SIDs

Expected results:
Should translate these SIDs to Domain Users and Groups

Additional info:

Patches for this ticket are welcome.

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
milestone: NEEDS_TRIAGE => SSSD Patches welcome
review: True => 0
selected: =>
testsupdated: => 0

Metadata Update from @lslebodn:
- Issue set to the milestone: SSSD Patches welcome

2 years ago

||When I go to the properties of a directory in the test share on this machine from Windows and select the ||security tab, I just see the SID's and not the names of the domain users.
I cannot repro it, I only see AD users. I see 'amit@gsslab.pnq.redhat.com' not SID.
# ls -ld /share/
drwxrwxrwx 3 amit@gsslab.pnq.redhat.com domain users@gsslab.pnq.redhat.com 18 Apr 9 12:52 /share/

# alternatives --set libwbclient.so.0.13-64 /usr/lib64/sssd/modules/libwbclient.so.0.13.0
# alternatives --display libwbclient.so.0.13-64
libwbclient.so.0.13-64 - status is manual.
link currently points to /usr/lib64/sssd/modules/libwbclient.so.0.13.0
/usr/lib64/samba/wbclient/libwbclient.so.0.13 - priority 10
/usr/lib64/sssd/modules/libwbclient.so.0.13.0 - priority 20
Current `best' version is /usr/lib64/sssd/modules/libwbclient.so.0.13.0.

@amitkumar25nov, you have to check the permissions on the Windows client not on the Linux file-system. Additionally you have to make sure that "use_fully_qualified_names = False" is used to reproduce the issue from https://bugzilla.redhat.com/show_bug.cgi?id=1323771.

The proper solution here is quite complex because SSSD must return more information than needed for the plain nss calls like getpwnam(), namely the short user name and the fully-qualified and the short domain name. To perform well the memory mapped cache must be aware of the additional data as well. I've send an initial patch set some months ago but especially the memory mapped cache related part needs more work.

Metadata Update from @sbose:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None

a year ago

Login to comment on this ticket.