Bug #24230
closedUser management - Bug #24219: Display user detail using information from database
Authentication providers and role mapping settings should be exposed
Description
- 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 ?
Updated by Clark ANDRIANASOLO 9 months ago
- Related to User story #22738: OIDC provided custom role list added
Updated by Clark ANDRIANASOLO 9 months ago
- Related to Bug #23254: User management plugin incorrectly understands OIDC roles added
Updated by Clark ANDRIANASOLO 9 months ago
- Subject changed from Authentication providers and role mapping should be statically known to Authentication providers and role mapping settings should be exposed
- Description updated (diff)
Updated by Clark ANDRIANASOLO 9 months ago
- Status changed from New to In progress
Updated by Clark ANDRIANASOLO 9 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/5408
Updated by Vincent MEMBRÉ 9 months ago
- Target version changed from 7.3.12 to 7.3.13
Updated by Clark ANDRIANASOLO 9 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|322b08ab0848de40479097377d7092648b9a78b3.
Updated by Clark ANDRIANASOLO 9 months ago
Applied in changeset rudder|9a18100f2b83c25abfa3f0e27a46942fffa334dc.
Updated by Clark ANDRIANASOLO 9 months ago
Applied in changeset rudder|9a18100f2b83c25abfa3f0e27a46942fffa334dc.
Updated by Clark ANDRIANASOLO 9 months ago
Applied in changeset rudder|50a55020a62609c2cc2a7c8bcea88018891b0e97.
Updated by Clark ANDRIANASOLO 9 months ago
Applied in changeset rudder|50a55020a62609c2cc2a7c8bcea88018891b0e97.
Updated by Clark ANDRIANASOLO 9 months ago
Applied in changeset rudder|c04b01d3efac037216e3a3d853008daaa65ce732.
Updated by Clark ANDRIANASOLO 9 months ago
Applied in changeset rudder|c04b01d3efac037216e3a3d853008daaa65ce732.
Updated by Clark ANDRIANASOLO 9 months ago
Applied in changeset rudder|d741fc7a4ca00e99368975ab2cbcb1e3eecb6556.
Updated by Clark ANDRIANASOLO 9 months ago
Applied in changeset rudder|d741fc7a4ca00e99368975ab2cbcb1e3eecb6556.
Updated by Anonymous 9 months ago
Applied in changeset rudder|ed0a64c28feb2519f9e18fcfc903ef5ecd10fd03.
Updated by Vincent MEMBRÉ 9 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.3.13 which was released today.