-
Notifications
You must be signed in to change notification settings - Fork 113
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
in memory user provider #2781
in memory user provider #2781
Conversation
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
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.
Looks fine to me overall. I just wonder, didn't we agree to just use the a separate instance of the machine auth provider for auth. That way we would just need the new userprovider. I might be mixing things up though.
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
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.
LGTM
We added an in memory implementation for the user provider that reads the users from the mapstructure passed in.
We will use it to configure a second minimal gateway with a single system user for the metadata storage to keep it completely independent of the normal users.
See owncloud/ocis#3343