Winsync & Passsync are really great additions in aiding intolerability of 389 and AD.
Are there any plans for adding a SAMBA4 plugin so that the same can be achieved?
Samba Support
The full up-to-date list is here - http://wiki.samba.org/index.php/Samba4/LDAP_Backend Passwords Support several different kinds of password encryption/hashing: all of the Kerberos KDC types heimdal is slightly different than MIT NT (utf8-uc2-md4) LM (des)
Replying to [ticket:47870 stuartiannaylor]:
Winsync & Passsync are really great additions in aiding intolerability of 389 and AD. Are there any plans for adding a SAMBA4 plugin so that the same can be achieved? Samba Support The full up-to-date list is here - http://wiki.samba.org/index.php/Samba4/LDAP_Backend Passwords Support several different kinds of password encryption/hashing: all of the Kerberos KDC types heimdal is slightly different than MIT NT (utf8-uc2-md4) LM (des)
You might want to take a look at IPA (IdM) which supports samba and kerberos passwords.
Lol not sure about intolerability :) interoperability I think.
IPA is just overboard. The 389 winsync & passsync is just brilliantly simple.
Its there for windows and for simple server setup's like I say its really good.
Would just be great if the exact same mechanism and plugin was available for Samba4
We have no plan to implement samba4 plugin.
But your contribution would be greatly appreciated.
#48876 will provide the hooks to implement this.
Metadata Update from @firstyear: - Issue set to the milestone: FUTURE
Metadata Update from @firstyear: - Issue assigned to firstyear
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1201
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.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: duplicate)