Re: [389-users] Password sync

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hugo Etievant wrote:
Michael Ströder a écrit :
Hugo Etievant wrote:
Password is captured in clear by passsync service into the AD server
witch is used by workstation for changing password operation.

Out of curiousity: What happens if the passsync service cannot reach the
FDS via LDAP because of network problems? Is the password synch LDAP
modify operation synchronous or is there kind of a queue implemented?


log file of passsync service show that password change is deferring for each user in case of network problem or bad access right to LDAP, constraint violation, etc... until change is abandonned

sample :
01/21/09 15:35:33 Deferring password change for xxx
01/21/09 15:36:12 Deferring password change for xxx
01/21/09 15:37:29 Deferring password change for xxx
[...]
01/21/09 15:39:47 Abandoning password change for xxx backoff expired
Check the access log and errors log for the directory server to see if you can figure out why the password change was not accepted, if not a network problem.

<<attachment: smime.p7s>>

--
389 users mailing list
389-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users

[Index of Archives]     [Fedora Directory Users]     [Fedora Directory Devel]     [Fedora Announce]     [Fedora Legacy Announce]     [Kernel]     [Fedora Legacy]     [Share Photos]     [Fedora Desktop]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux