-
Notifications
You must be signed in to change notification settings - Fork 189
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
User assignments-list gets longer after every restart on default users #3432
Comments
Some notes: This only happens when using the "metadata" storage for settings (which is our default since a few weeks). When using "metadata" the default assignments are only created when processing the first (wrirte) request on the settings API. |
could not reproduce on 7f68049 (post 2.0.0rc.1) |
This but is definitely still present in current master:
now list assignments:
Having the admin role assigment twice is already a bug. But when you restart restart ocis and list assignments again you get it listed 4 times.:
I think this only happens for admin and demo-users. |
When using the metadata storage (the current default) the default role assignments were recreated at every start of the settings service. Leading to duplicated role assignments Fixes: owncloud#3432
When using the metadata storage (the current default) the default role assignments were recreated at every start of the settings service. Leading to duplicated role assignments Fixes: owncloud#3432
Describe the bug
User assignments-list gets longer after every restart on default users
Steps to reproduce
Steps to reproduce the behavior:
{ "account_uuid": "058bff95-6708-4fe5-91e4-9ea3d377588b" }
{ "account_uuid": "058bff95-6708-4fe5-91e4-9ea3d377588b" }
Expected behavior
The assignment list should not have more items after kill and start ocis for no reason
Actual behavior
User assignments-list gets longer after every restart on default users
Setup
Please describe how you started the server and provide a list of relevant environment variables.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: