You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IMO the implementation must have 0 or 0x7FFFFFFFFFFF (9223372036854775807) as "no expire" and the value as the number of 100 nanosecond intervals from January 1, 1601 (UTC) (aka filetime).
This is the expire specification for MS Active Directory
Sorry, IIRC the implementation was written for OpenLDAP and we had no users with AD available for checking. A PR would be probably t best way to fix it. At least I have no AD for testing available.
@jensens@rnixx thank you. Yes, I know, sorry if there was a misunderstanding.
My intention was to open a feature request if someone need/wants to implement it.
Otherwise if no one does, in my OSS contribution time or with a customer request, I can do a PR with the implementation.
In
pas.plugins.ldap
andnode.ext.ldap
(https://github.com/conestack/node.ext.ldap/blob/299f3c056570d80b0e4346ffe441490489bade63/src/node/ext/ldap/ugm/expires.py#L105) I cannot find an implementation for account expire in MS Active Directory.IMO the implementation must have 0 or 0x7FFFFFFFFFFF (9223372036854775807) as "no expire" and the value as the number of 100 nanosecond intervals from January 1, 1601 (UTC) (aka
filetime
).This is the expire specification for MS Active Directory
https://learn.microsoft.com/en-us/windows/win32/adschema/a-accountexpires
The text was updated successfully, but these errors were encountered: