Reply to self: Sorry, user error. sudo cat /etc/samba/smbpasswd | smbldap-migrate-pwdump-accounts ... leaves the perl process without sufficient privileges to access smbtools_bind.conf.
Moving "modify_account" to the end of the file still seems like a good idea. If smbpasswd is the intended input, updating gecos doesn't make much sense. The 5th field in that file is actually sambaAcctFlags On Wed, Mar 26, 2014 at 11:49 AM, Andy Theuninck <[email protected]> wrote: > I'm trying to use the migration-tools to add smb attributes to > existing LDAP user accounts. The smbldap-migrate-unix-accounts script > worked flawlessly and added objectClass=sambaSamAccount and sambaSID > fields to the relevant accounts. I think that means my smbldap.conf > and smbldap_bind.conf are set up correctly. > > I had to move the "modify_account" to the bottom of the file to get > smbldap-migrate-pwdump-accounts to run at all (perl complained about > the usage of $ldap_master in the subroutine before it had been > declared in the main scope). But the "is_samba_user" subroutine always > returns false. If I run identical searches using ldapseach, I get > results. > > I also tried adding a separate lookup based on get_user_entry in > smbldap-migrate-unix-accounts (which works). That also never locates > the correct user account. Is there a newer/better way to migrate > existing smbpasswd info into LDAP? The very latest version doesn't run > out of the box because of the scoping issue so I'm wondering if it's > been abandoned. > > Patch of what I've tried (doesn't work, other than resolving the scope > problem): > http://gohanman.com/smbldap-migrate-pwdump-accounts.patch > > Any ideas or assistance would be appreciated. _______________________________________________ Smbldap-tools-tech mailing list [email protected] https://mail.gna.org/listinfo/smbldap-tools-tech
