Learn more about these different git repos.
Other Git URLs
Now that SSSD AD integration (#996) is available it would be desirable to be able to use SSSD instead of Winbind with smbd to allow completely replacing Winbind also on servers providing Samba shares in AD domains. Ideally SSSD could provide the same interfaces Winbind provides today for smbd removing the need for smbd changes/updates thus allowing smooth transition from Winbind to SSSD on Samba servers.
Additionally, this should remove the need for using username map script [1] which is currently required if one wants to mix local/NSS groups and domain groups to restrict access to Samba shares when using security = ads. (This request is forked into a separate ticket #1591)
1) https://lists.samba.org/archive/samba-technical/2012-October/088039.html
Sort of dup of the #1573. I am not sure with one should be closed.
milestone: NEEDS_TRIAGE => SSSD 1.10 beta priority: major => critical summary: RFE: Allow SSSD to be used with smbd shares => [RFE] Allow SSSD to be used with smbd shares type: feature => enhancement
Fields changed
description: Now that SSSD AD integration (#996) is available it would be desirable to be able to use SSSD instead of Winbind with smbd to allow completely replacing Winbind also on servers providing Samba shares in AD domains. Ideally SSSD could provide the same interfaces Winbind provides today for smbd removing the need for smbd changes/updates thus allowing smooth transition from Winbind to SSSD on Samba servers.
Additionally, this should remove the need for using username map script [1] which is currently required if one wants to mix local/NSS groups and domain groups to restrict access to Samba shares when using security = ads.
1) https://lists.samba.org/archive/samba-technical/2012-October/088039.html => Now that SSSD AD integration (#996) is available it would be desirable to be able to use SSSD instead of Winbind with smbd to allow completely replacing Winbind also on servers providing Samba shares in AD domains. Ideally SSSD could provide the same interfaces Winbind provides today for smbd removing the need for smbd changes/updates thus allowing smooth transition from Winbind to SSSD on Samba servers.
rhbz: => todo
Might be a dup of #1573.
design: => design_review: => 0 fedora_test_page: => selected: => May
priority: critical => major
milestone: SSSD 1.10 beta => SSSD 1.11 beta review: => 0
changelog: => milestone: SSSD 1.12 beta => Interim Bucket
priority: major => critical
milestone: Interim Bucket => SSSD 1.12 beta
owner: somebody => sbose status: new => assigned
Please rescope if something is missing or close if everything will be done in Samba. Thanks!
milestone: SSSD 1.12 beta => NEEDS_TRIAGE
I'm working to get the support into samba upstream but it would be nice to keep this ticket as a tracker. I've changed the type to task to indicate that no coding is needed here.
type: enhancement => task
milestone: NEEDS_TRIAGE => SSSD 1.13 beta
milestone: SSSD 1.13 beta => NEEDS_TRIAGE
milestone: NEEDS_TRIAGE => SSSD 1.12.1
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1109331 (Red Hat Enterprise Linux 7)
rhbz: todo => [https://bugzilla.redhat.com/show_bug.cgi?id=1109331 1109331]
patch: 0 => 1
resolution: => fixed status: assigned => closed
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1164428 (Red Hat Enterprise Linux 6)
rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=1109331 1109331] => [https://bugzilla.redhat.com/show_bug.cgi?id=1109331 1109331], [https://bugzilla.redhat.com/show_bug.cgi?id=1164428 1164428]
Metadata Update from @myllynen: - Issue assigned to sbose - Issue set to the milestone: SSSD 1.12.1
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/2630
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.