-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
LDAP to not register new users when outside of fair use or over limits #33945
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
Conversation
Signed-off-by: Arthur Schiwon <[email protected]>
|
Downside of the current solution: With on-demand mapping, an end user may face an infinite spinner when trying to share a file, when a user would have to be mapped. The sharing frontend code does not handle well 500 results. My idea now is to perhaps react on the request: throw the exception only when the request is done via provisioning api, otherwise just skip mapping. |
- unbreaks functionality for end users when on demand mapping takes place Signed-off-by: Arthur Schiwon <[email protected]>
- do not stack notifications, replace them - and replace them once a day only - with LDAP it might end in total spam terror (also push) otherwise Signed-off-by: Arthur Schiwon <[email protected]>
2fc503c to
7d3457e
Compare
|
/backport to stable25 |
|
/backport to stable24 |
Co-authored-by: Simon L. <[email protected]> Signed-off-by: blizzz <[email protected]>
PVince81
left a comment
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.
👍 code looks fine
szaimen
left a comment
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.
🐘
|
Can someone restart drone? Not sure if the failure is really related... |
|
yeah, a bit weird: I've restarted the Drone builds |
In
UserManager::createUserwe check whether the instance is over limits (subscription or one-click-instance) and would refuse to add users. It works for local backends only. This PR offers a comfort method for assertion and makes the LDAP backend taking advantage of it.