fix(user_ldap): fix lastLogin reading wrong appid and configkey#59415
Conversation
|
/backport to stable33 |
susnux
left a comment
There was a problem hiding this comment.
Thank you so much for looking into this!
The error message is so unrelated and confusing...
|
@hamidout to be able to merge your PR we need you to sign-off your commit, see: You can do so by e.g. |
fetchDetails() was calling getValueInt($uid, 'user_ldap', 'email') instead of getValueInt($uid, 'login', 'lastLogin'), causing lastLogin to always return 0 for offline LDAP users. Fixes nextcloud#58421 Signed-off-by: hamid <hamid@webpick.net>
6aaa258 to
b7d6822
Compare
|
Thanks for your first pull request and welcome to the community! Feel free to keep them coming! If you are looking for issues to tackle then have a look at this selection: https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22 |
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
Fixes #58421
Summary
fetchDetails()inOfflineUserwas using the wrong appid (user_ldap) and key (email) when readinglastLoginviagetValueInt(). The value is stored under appidloginwith keylastLogin(as written byUser::updateLastLoginTimestamp()), so this always returned 0 for offline LDAP users.TODO
Checklist
AI (if applicable)