Only a subset of
attributes is sync between AD and 389 ds. However by performing
ldapsearch request over the AD and ldapmodify on the corresponding entry in 389
ds , you can create a script which merge semi-automatically some other
attributes. For password sync,
like said by solarflow, the Microsoft hash algorithm can t be used on other
system. This is the reason why password sync service only deals with password
in plain text format by adding a hook on the password change event. De :
389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx [mailto:389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx]
De la part de solarflow99 I meant to say: can't use the windows password hash On Tue, Nov 15, 2011 at 12:43 AM, solarflow99 <solarflow99@xxxxxxxxx> wrote: I had a similar setup as yours, for #1 I think I did have to use 389
console to enable posix attributes so the user could login to linux, i'm not
sure how to make this automatic. For #2 this is because windows passwords
are encrypted differently, and linux can use the windows password hash.
2011/11/15 Walter Neu <w.neu@xxxxxxxxxxx> Hi all, -- |
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users