Jeff Gamsby wrote:
Here is a piece of the log:
This tells me that FDS either a) succeeded in modifying the user's password
or b) it never tried to generate the modify. It isn't clear from the log
what the
two modify operations in the changelog are (why are there two??).
Can you say more ab
Thanks, I'll try to generate the UnicodePwd and run ldapmodify.
Here is a piece of the log:
[14/Jun/2006:11:14:37 -0700] NSMMReplicationPlugin - agmt="cn=AD"
(ad:636): State: ready_to_acquire_replica -> wait_for_changes
[14/Jun/2006:11:14:37 -0700] NSMMReplicationPlugin - ruv_update_ruv:
succe
Can the OP post a verbose log segment relating to this problem please ?
There _should_ be something in the log to indicate where the problem lies.
--
Fedora-directory-users mailing list
Fedora-directory-users@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-directory-users
UnicodePwd has to be little-endian unicode and with quotes around it.
You can do something like...
echo \"Secret12\" > pass.txt
iconv -t UNICODELITTLE -o unicodepass.txt pass.txt
And then base64 encode unicodepass.txt and use the result for unicodePwd
value.
I got the details from http://su
Correct. It was not enabled when I first installed and configured
PassSync. I tried to use ldapmodify to change the password, but that
didn't work either.
To use ldapmodify, do I change UnicodePwd?
How do I generate UnicodePwd?
dn: cn=user,cn=users,dc=ad,dc=server,dc=com
changetype: modify
re
Jeff Gamsby wrote:
Thanks for responding.
I have windows 2000, the default password policy is disabled by
default, but I did turn it on to see if that was the problem and also
tried more complex passwords when testing. Nothing has worked so far.
I'm not even sure if there is any other tests t
Thanks for responding.
I have windows 2000, the default password policy is disabled by default,
but I did turn it on to see if that was the problem and also tried more
complex passwords when testing. Nothing has worked so far. I'm not even
sure if there is any other tests that I can do, I've t
When i add user or change password at fds side , it stuck with windows
(2003) default password policy.
So i have to chage to more strict password or disable policy at ads ,
then fds sync with ads completely.( can log on to ads with same password as
fds user)
im not sure this is same case
