-
Notifications
You must be signed in to change notification settings - Fork 40
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
Implement soft auto provisioning #730
Conversation
654b0a2
to
679c111
Compare
lib/Service/ProvisioningService.php
Outdated
$this->eventDispatcher->dispatchTyped(new UserChangedEvent($user, 'displayName', $newDisplayName, $oldDisplayName)); | ||
} | ||
} else { | ||
$user->setDisplayName($newDisplayName); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure here if the $newDisplayName in L112 is always set as its only set once when the if condition in L101 was triggered
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch! Thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please check my comment regarding $newDisplayName in ProvisioningService.php
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! :)
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! |
8f28992
to
a1a85a4
Compare
3b584ed
to
c48a5f5
Compare
@juliushaertl Could you check if this PR makes sense? 😁 |
c48a5f5
to
cb658a2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The approach looks good to me, haven't tested though 👍
…login, update their info Signed-off-by: Julien Veyssier <[email protected]>
Signed-off-by: Julien Veyssier <[email protected]>
Signed-off-by: Julien Veyssier <[email protected]>
…isioning Signed-off-by: Julien Veyssier <[email protected]>
Signed-off-by: Julien Veyssier <[email protected]>
cb658a2
to
d52b05b
Compare
Signed-off-by: Julien Veyssier <[email protected]>
Would it be possible to catch this Problem during while this provisioning? |
Problem: When auto provisioning is enabled, if a user with the same ID exists in another backend (Db, LDAP...), we create a second user in the user_oidc backend which leads to issues and confusion.
Here is a partial solution to this problem:
New config
soft_auto_provision
flag (enabled by default).This does not migrate existing users to the user_oidc backend but allows them to log in without creating a duplicate user.
Nothing was changed when auto provisioning is disabled.
Extra change: In the user backend, the ldap sync was not triggered when looking for an existing user.