Learn more about these different git repos.
Other Git URLs
This ticket changed its shape. The CIFS client and server side tickets have been forked out as separate tickets. https://fedorahosted.org/sssd/ticket/1534 https://fedorahosted.org/sssd/ticket/1573
The scope of this ticket is reduced to AD provider must support trusted domains in the similar way how ipa provider does it.
Fields changed
owner: somebody => sbose status: new => assigned
milestone: NEEDS_TRIAGE => SSSD 1.2
milestone: SSSD 1.2 => SSSD 1.3
milestone: SSSD 1.3 => SSSD 2.0
I currently use 389, Samba 3, and sssd. Windows clients can interact with Samba/389 just fine. Linux clients can use sssd/389 just fine, too. However, if a Linux user wants to keep a Windows workstation as well, they have to use smbldap-tools, or Windows, to set the Samba password in the port389 database so that their password is in sync between the UNIX and NT worlds.
IMHO, the simplest way to have sssd interact with Samba is to mimic the functionality of the smbldap-passwd perl script. Then linux clients can change passwords with traditional tools.
Samba 4 will be a different beast (built-in LDAP) so there may need to be split bugs for Samba3/4. Currently RHEL and Fedora only ship Samba 3 binaries (the samba 4 packages are libraries only, no daemons/tools) so it would be nice, and should be trivial, to add simple password support for at least Samba 3.
cc: => mooninite coverity: => upgrade: => 0
milestone: SSSD 2.0 => NEEDS_TRIAGE
This is the effort pzuna investing his time in at the moment.
milestone: NEEDS_TRIAGE => SSSD 1.7.0 owner: sbose => pzuna status: assigned => new
component: Data Provider => Winbind Provider patch: => 0
milestone: SSSD 1.7.0 => SSSD 1.6.0 summary: Implement Samba provider => Implement Winbind provider
milestone: SSSD 1.6.0 => SSSD 1.8.0
milestone: SSSD 1.8.0 => NEEDS_TRIAGE rhbz: =>
milestone: NEEDS_TRIAGE => SSSD 1.8 AD Integration NEEDS TRIAGE
milestone: SSSD 1.8 AD Integration NEEDS TRIAGE => SSSD Deferred owner: pzuna =>
rhbz: => 0
blockedby: => blocking: => component: Winbind Provider => AD Provider description: Reach out to the Samba community and desing and implement the best solution for the SSSD and Samba integration. Requires research. => Reach out to the Samba community and desing and implement the best solution for the SSSD and Samba integration. Requires research.
There are several requirements in this area: 1) SSSD should be able to interoperate with CIFS client and provide enough info for it so that winbind is not needed any more 2) It should dynamically recognize trusted AD domains in AD provider
This is a major feature. feature_milestone: => milestone: SSSD Deferred => Temp milestone priority: minor => critical proposed_priority: => Blocker summary: Implement Winbind provider => [RFE] Winbind feature parity
rhbz: 0 => todo
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=847870 (Red Hat Enterprise Linux 7)
rhbz: todo => [https://bugzilla.redhat.com/show_bug.cgi?id=847870 847870]
Moving all the features planned for 1.10 release into 1.10 beta.
milestone: Temp milestone => SSSD 1.10 beta
priority: critical => blocker
rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=847870 847870] => [https://bugzilla.redhat.com/show_bug.cgi?id=847870 847870], [https://bugzilla.redhat.com/show_bug.cgi?id=819657 819657]
description: Reach out to the Samba community and desing and implement the best solution for the SSSD and Samba integration. Requires research.
This is a major feature. => This ticket changed its shape. The CIFS client and server side tickets have been forked out as separate tickets. https://fedorahosted.org/sssd/ticket/1534 https://fedorahosted.org/sssd/ticket/1573
The scope of this ticket is reduced to AD provider must support trusted domains in the similar way how ipa provider does it. summary: [RFE] Winbind feature parity => [RFE] Recognize trusted domains in AD provider
design: => design_review: => 0 fedora_test_page: => selected: => Want
priority: blocker => critical
review: => 0
owner: => jhrozek patch: 0 => 1 status: new => assigned
design: => https://fedorahosted.org/sssd/wiki/DesignDocs/GlobalCatalogLookups design_review: 0 => 1
changelog: => If the SSSD client is joined to a Windows domain which is part of a forest, Global Catalog lookups should be able to resolve all users and groups in the forest and not only the ones from the joined domain.
rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=847870 847870], [https://bugzilla.redhat.com/show_bug.cgi?id=819657 819657] =>
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=969883
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=847870 847870], [https://bugzilla.redhat.com/show_bug.cgi?id=819657 819657], [https://bugzilla.redhat.com/show_bug.cgi?id=969883 969883]
rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=847870 847870], [https://bugzilla.redhat.com/show_bug.cgi?id=819657 819657], [https://bugzilla.redhat.com/show_bug.cgi?id=969883 969883] => [https://bugzilla.redhat.com/show_bug.cgi?id=969883 969883]
resolution: => fixed status: assigned => closed
Metadata Update from @sgallagh: - Issue assigned to jhrozek - Issue set to the milestone: SSSD 1.10 beta
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/1406
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.