On 20/05/2010 10:57, Romain wrote:
Le 19/05/2010 20:55, Jonathan Clarke a écrit :
Le 19/05/2010 19:33, Jonathan Clarke a écrit :
Which says:
"The date and time that the password for this account was last changed.
This value is stored as a large integer that represents the number of
100 nanosecond intervals since January 1, 1601 (UTC)."
So 1, means 100 nanoseconds after January 1, 1601 - an unlikely value
:-)
Basically, you need to put a valid value in this field. LSC has support
for reading a field like this (getNumberOfWeeksSinceLastLogon in the
org.lsc.utils.AD class), but not for writing. Maybe we should
implement it.
I just added some methods to the AD class to convert to and from AD
timestamps like this one. They can convert to and from Unix timestamps.
See http://tools.lsc-project.org/issues/217.
Do you think any other formats would be useful?
Jonathan
So I am obliged to change password ? I have not understand all you have
said.
All I'm saying is that I've added some functions to the next version of
LSC to make updating dates in AD easier.
It appears that the obligation to change password is related to the
field "pwdLastUpdated", which is a date, so that's why I mentioned these
functions.
Jonathan
--
--------------------------------------------------------------
Jonathan Clarke - [email protected]
--------------------------------------------------------------
Ldap Synchronization Connector (LSC) - http://lsc-project.org
--------------------------------------------------------------
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
