Ticket #1534 (closed enhancement: fixed)
[RFE] Integrate SSSD with CIFS client
|Reported by:||dpal||Owned by:||sbose|
|Priority:||blocker||Milestone:||SSSD 1.12 beta|
|Coverity Bug:||Patch Submitted:||no|
|Red Hat Bugzilla:||922081||Design link:||https://fedorahosted.org/sssd/wiki/DesignDocs/IntegrateSSSDWithCIFSClient|
|Design review:||no||Fedora test page:|
|Chosen:||Must||Candidate to push out:||no|
|Release Notes:||With version 5.9 of cifs-utils a plugin interface was introduced to allow services other than winbind to handle the mapping of POSIX UIDs and SIDs. SSSD provides a plugin to allow the cifs-utils to ask SSSD to map the ID. With this plugin an SSSD client can access a CIFS share with the same functionality as a client running Winbind.|
Here is a mail thread on the subject:
Do you know, can sssd 1.5 be used with cifs client to mount Windows shares? AFAIU yes if the AD uses POSIX extensions otherwise one has to use SSSD 1.9 or winbind to do id mapping, correct? Or there is some close connection between cifs client and winbind and they talk to each other directly?
In general mounting Windows shares is a completely orthogonal business from resolving users. The only case when CIFS may need that is to manipulate ACLs. I CCed Jeff that may shed a light on whether we have any dependency on Winbind at the moment.
We have a couple of relatively recent additions to cifs-utils that link in libwbclient to do SID to uid/gid conversions:
/usr/bin/getcifsacl /usr/bin/setcifsacl /usr/sbin/cifs.idmap
What are you looking to do, specifically? Would it be possible to add a plugin interface here, so that e.g. sssd can provide a library which does the SID<->uid/gif mapping instead of winbind? And place the default winbind plugin provided by cifs-utils in a separate package so that the cifs-uitls package does not have any dependency to libwbclient?
Sure, I guess. I'm not sure I understand the point though -- what's the rationale for removing the dependency on winbind? sssd has a special provider for AD which offers similar functionality like pam_winbind/nss_winbind together with a running winbind. The goal for the next sssd release 1.10 is to reach feature parity with winbind with respect to PAM and NSS so that winbind does not need to run on a system with sssd. Especially sssd will to his own SID to uid/gid mapping. The scheme is based on autorid and can be made compatible with autorid (in the limits of autorid), but it would be quite an overhead if winbind must be run just to map the IDs for the cifs-utils.
Ok, I think that's basically going to mean rewriting these utils from scratch. They aren't very large, but most of the code deals with wbcDomainSid pointers internally. The code uses these functions currently, so we'd need to replace them with generic variants for this new API:
wbcStringToSid wbcSidToUid wbcLookupSid wbcGetpwnam wbcUidToSid
comment:10 Changed 3 years ago by dpal
- Candidate to push out unset
- Milestone changed from SSSD 1.12 beta to Interim Bucket
comment:13 Changed 3 years ago by sbose
- Owner changed from somebody to sbose
- Status changed from new to assigned
comment:16 Changed 3 years ago by sbose
- Status changed from assigned to closed
- Resolution set to fixed
- Milestone changed from NEEDS_TRIAGE to SSSD 1.12 beta
comment:17 Changed 3 years ago by jhrozek
- Red Hat Bugzilla changed from todo to [https://bugzilla.redhat.com/show_bug.cgi?id=922081 922081]