Actions
Bug #24230
closedUser management - Bug #24219: Display user detail using information from database
Authentication providers and role mapping settings should be exposed
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Small
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
Currently, enabling providers and allowing to override their role is done in the auth-backends plugin :
- for ldap, we parse the
rudder.auth.provider
configuration property for anldap
attribute, if found we always map its roles using the users XML file - for oauth2 and oidc, we parse the
rudder.auth.provider
configuration property for the respective attributes, if found we can :
1. take the users XML file into account to add roles to provided users (default behavior)
2. enable role provisioning along user provisioning from the configuration value :rudder.auth.oauth2.provider.{registration}.roles.enable=true
3. disallow extending user roles from the users XML file by providing a configuration value :rudder.auth.oauth2.provider.{registration}.roles.override=true
, whereregistration
is priorly defined with a configuration property :rudder.auth.oauth2.registrations
- what is the provider internal id ?
- is user role provisioning enabled by the provider ?
- if roles can be provisioned, does the provider extend roles or strictly override them ?
Actions