Hi Attila, thanks for the update. This is now fixed in the development version. There was a small typo:
https://github.com/LDAPAccountManager/lam/commit/52b85ae6e8c006850e68dfe27bc2b8d44c4dd99b You can apply it manually to: /usr/share/ldap-account-manager/lib/modules/posixAccount.inc The fix will be part of the September release. Best regards Roland Am 09.08.22 um 13:16 schrieb KATONA Istvan-Attila:
*This email contains one or more catchphrase(s), like password/passwort, voicemail, etc. which may be used by attackers.* Hi, (sorry for the banner/warning above, it is added by our mailserver and it's beyond my control) Thanks for your reply. I checked and this is not an issue in our case, the shadowLastChange attribute can be read (and also written actually) by the user, and it is also confirmed in the lam.log (logLevel set to 7), shadowLastChange is printed among the other attributes when the user logs into SelfService. I can also add it to the page from the SelfService profile configuration and it's printed correctly. Self-service is configured to use the authenticated user (no LDAP user/password filled out and "Use for all operations" is not checked). I still had an old testsystem with LAM Pro 7.4 installed, tested the SelfService password change and it updates shadowLastChange to the current date. Then I proceeded to uninstall 7.4, installed LAM Pro 8.0.1 and tested again the password change, shadowLastChange is no longer updated. No OpenLDAP settings were changed during the process. I think there must be some change somewhere between 7.4 and 8.0.1 that changed the behaviour. Thanks for your time. Best regards, Attila _______________________________________________ Lam-public mailing list Lam-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lam-public
_______________________________________________ Lam-public mailing list Lam-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lam-public
