-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
When creating a role mapping through the CLI using a non-formal role name like "AUDITOR", that role name is used as-is in the persistent configuration:
cd /core-service=management/access=authorization ./role-mapping=AUDITOR:add ./role-mapping=AUDITOR/include=johndoe:add(name=johndoe,type=user)
The persistent configuration should map non-formal role names to formal role names, as other management clients (the console) rely on the formal names.
- duplicates
-
WFLY-2270 Lack of model integrity checking regarding role mappings, standard role names and scoped role names.
- Closed