Actions
Bug #25280
closed
Clarify that we do not support authorizations in OIDC authentification role in documentation
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
In documentation, we say:
You can configure an OAuth2 or OIDC provider so that it informs Rudder of the roles the user need to have. This allows to centrally manage both user and authorisation in the same place. This feature works with the custom roles feature provided by the user-management plugin. Please see that linked documentation to understand how custom roles work in Rudder.
We should explicitly say that every authorisation are not supported like node_all rule_read technique_write etc
Only built in role and custom role can be used
Updated by Elaad FURREEDAN 4 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Elaad FURREEDAN to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-plugins/pull/743
Updated by Anonymous 4 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder:rudder-plugins|67dfc31bbeb16afbb2f68b646b51f3aaee7b5f7d.
Updated by Vincent MEMBRÉ 2 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder plugin auth-backends v8.2.0.beta1-2.7
Updated by Vincent MEMBRÉ about 2 months ago
This bug has been fixed in Rudder plugin auth-backends v8.1.7-2.7
Actions