-
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
no oCIS roles with LDAP user backend #2646
Comments
@ishank011 Any idea how to bring back the ocis roles into the token? Could we somehow pass them down with the AuthenticateRequest in https://github.com/owncloud/ocis/blob/master/proxy/pkg/user/backend/cs3.go#L34? That would of course mean that we need to add another GetUserByClaim() call to lookup the user before that. |
This we use reva to mint tokes for users when using the CS3 backend (owncloud#2528) the user's roles are no longer part of the token. This adds a workaround to the RequireSelfOrAdmin middleware to Request the user's role id on demand from the settings service. Partial Fix for owncloud#2646
This we use reva to mint tokes for users when using the CS3 backend (owncloud#2528) the user's roles are no longer part of the token. This adds a workaround to the RequireSelfOrAdmin middleware to Request the user's role id on demand from the settings service. Partial Fix for owncloud#2646
This we use reva to mint tokes for users when using the CS3 backend (owncloud#2528) the user's roles are no longer part of the token. This adds a workaround to the RequireSelfOrAdmin middleware to Request the user's role id on demand from the settings service. Partial Fix for owncloud#2646
@rhafer do you know about the current state? |
Basically the above mentioned workaround are still in place I think. We're adding the roleID to the context in the account_resolver middleware in the proxy as well nowadays IIRC. |
Ok, than I'm closing this for now, since the bug description is no longer valid. Fixed by #3096 |
Describe the bug
Since the we now use reva's Authenticate method to Mint Tokens, the tokens no longer contain the user's oCIS roles (at least when using the CS3 account backend). So thinks like ReadRoleIDsFromContext, which rely on the roleIDs being present in the token, no longer work.
Steps to reproduce
Expected behavior
Settings are available
Actual behavior
Setup
CS3 users deployment example
Additional context
The text was updated successfully, but these errors were encountered: