-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add FirstLoginListener to accept shares upon first ldap user login #30512
Conversation
7f7d082
to
2cc0113
Compare
8505af0
to
4b48b66
Compare
/rebase |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
4b48b66
to
ea2afb2
Compare
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
This does not work, the listener never gets called on neither of the 2 events according to the log… I do not understand the problem. Also, I’m wondering if this solution is enough, because it will only work for new users, not when adding an existing user to a group. |
[notes for myself] The idea is now to change the format of data stored by the update group background job so that we can easily search in it if a user/group association was already detected, and at login we browse known groups of the user, and if association is missing we announce it with a UserAddedEvent. |
Replaced by #40367 |
Trigger OCP\Group\Events\UserAddedEvent on first ldap user login for all his groups, to avoid having to wait on the background job before shares get accepted.
Signed-off-by: Côme Chilliet come.chilliet@nextcloud.com