Open shipperizer opened 5 months ago
I just realized something: normally this attribute would be updated by the server every time we perform a LDAP modify operation. At this time, GLAuth does not have LDAP modify operations since it's read-only.
I can think of two distinct scenario:
What use case are we trying to satisfy? If it's the proxy one, are we failing to forward the attribute?
design is for GLAuth to be acting as a proxy
we lost the ball on this but will try it and check that all works as expected and report back if something is missing
We are having issues when trying to integrate GLAuth with Apache Ranger
Ranger has a
usersync
functionality which periodically syncs from LDAP users and groups information using themodifyTimestamp
objectclass with the person or PosixAccountThe
modifyTimestamp
does not appear to be present in GLAuth, th value is used to optionally sync only changed entities since the last operation.could we have some directions on how to implement this in GLAuth?