On Wed, May 13, 2009 at 9:13 PM, John A. Sullivan III <jsullivan@xxxxxxxxxxxxxxxxxxx> wrote:
On Wed, 2009-05-13 at 15:06 -0400, John A. Sullivan III wrote:
> Hello, all. Several hours of googling and testing have not solved my
> problem. We are using Directory Server as our authentication mechanism
> for as much as possible in our environment. So far, we have integrated
> all our Linux servers, synchronized with AD, and are using it for
> Zimbra.
>
> We have just implemented a standalone SAMBA server and are having
> trouble synchronizing passwords. I see plenty of examples of how to
> have changes made using smbpasswd passed to the posix password in LDAP.
> But that's not what we want. We want users (some of whom use SAMBA and
> some of whom do not) to have a single place to change their password.
> The users are all KDE. Changing their passwords in the KDE control
> module for security changes everything brilliantly EXCEPT SAMBA.
>
> How do we make password changes executed by the users or by the LDAP
> admin in idm-console propagate to the SAMBA password attributes? Thanks
> - John
See if the allegated program smbpasswd-sync.pl can help. I use it for a similar purpose
against a Tivoli DIRECTORY SERVER. Do perldoc mbpasswd-sync.pl for the intended usage.
hth
Attachment:
smbpasswd-sync.pl
Description: Binary data
-- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
