Regex Policy Authorization is not working on fetching the RPT #20383

sridhar1495 · 2023-05-16T08:46:22Z

sridhar1495
May 16, 2023

Hi, I am trying to create the Authorization policy and permission using the Regex type that uses the attribute that is given in the group(group=admin, customAttribute=example).
My Configuration is as follows,

Step 1:

Created 'client scope' and inside that created 'Mapper' which is using the User Attribute and given the attribute name that is given in the group (i.e., customAttribute) and given the 'Token Claim Name = attribute'

Step 2:

Selected this scope in my Client's 'Client Scope'

Step 3:

In the 'Authorization' created Regex Policy and given the 'Target claim = attribute' and 'Regex Pattern=example'

Step 4:

I have used this policy in the permission which is having to be the access for the resource=profile and scope=read

Step 5:

I used the Evaluate tab in the authorization to check it before going to the token fetch. So I select the user who is joined to the 'admin' group that has the 'customAttribute=example'. And select the profile resource and Clicked the Evaluate Button.
It gives the result as permit for the Permission that I created in Step 4.

Step 6:

Since it is giving Permit I tried the token fetch. In both access_token and RPT token I am getting the attribute that is given in the group. But in the RPT token's authorization.permissions.scopes I am not getting the corresponding scope.

Expecting:
Can someone clarify that is there any issue in my configuration that needs to be configured in keycloak.

sridhar1495 · 2023-05-18T07:07:41Z

sridhar1495
May 18, 2023
Author

I have checked the behaviors and found it is bug in the evaluation engine during the RPT generation and created bug #20436

0 replies

Navigation Menu

Repository navigation

Regex Policy Authorization is not working on fetching the RPT #20383

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Regex Policy Authorization is not working on fetching the RPT #20383

Uh oh!

sridhar1495 May 16, 2023

Replies: 1 comment

Uh oh!

sridhar1495 May 18, 2023 Author

sridhar1495
May 16, 2023

sridhar1495
May 18, 2023
Author