ocis: rc.1 external OIDC+LDAP setup, error on new user first login
Describe the bug
I’m testing rc.1 with external OIDC+LDAP setup, when a new user try to login, /ocs/v1.php/cloud/user returned 500 error.
proxy service error log:
2022-11-13T13:51:24Z ERR Could not add default role error="{\"id\":\"ocis-settings\",\"code\":403,\"detail\":\"user has no role management permission\",\"status\":\"Forbidden\"}" service=proxy
2022-11-13T13:51:24Z ERR Could not get user by claim error="{\"id\":\"ocis-settings\",\"code\":403,\"detail\":\"user has no role management permission\",\"status\":\"Forbidden\"}" service=proxy
Seems like a bug, user shouldn’t need a role management permission to be assigned the default role.
(The one user set in the helm chart adminUUID option can login as the admin role)
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 29 (22 by maintainers)
Commits related to this issue
- Allow initial self-assignemnt of UserRole When using an external user management we need to allow users to self-assign the default role. This adds an explicit check for that to the settings service. ... — committed to rhafer/ocis by rhafer 2 years ago
- Allow initial self-assignemnt of UserRole When using an external user management we need to allow users to self-assign the default role. This adds an explicit check for that to the settings service. ... — committed to rhafer/ocis by rhafer 2 years ago
- Allow initial self-assignemnt of UserRole When using an external user management we need to allow users to self-assign the default role. This adds an explicit check for that to the settings service. ... — committed to rhafer/ocis by rhafer 2 years ago
- Allow initial self-assignemnt of UserRole When using an external user management we need to allow users to self-assign the default role. This adds an explicit check for that to the settings service. ... — committed to rhafer/ocis by rhafer 2 years ago
Found it:
This is weird. Why do we use the GraphAPI for Role Assignments? @kulmann @JanAckermann I thought we need to use the settings API for that purpose
Should be, yes. Needs re testing in the next qa cycle.