-
Bug
-
Resolution: Done
-
Major
-
None
-
RH-SSO-7.5.0
-
None
-
None
Hello Team,
[Problem Description]
OIDC User Realm Role Mapper does not handle single value token claim correctly
[Steps to Reproduce]
1) Create a new test OIDC client
2) Under Client > <My client> > Mappers , create a new mapper
The mapper type is User Realm Role, with the following settings as below
Claim Json Type is String
Multivalued is false
Add to ID token is false
Add to Access token is true
Add to user info is false
3) Create one role for the client and assign it to the user
4) Under Clients >Client Scopes > Evaluate
We would see :
"role_mapper_name": "[role_name]"
The cu expects:
"role_mapper_name": "role_name"