You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Audience mapper: included client audience not displayed
#44133
Problem description:
We are using Keycloak 26.2.4 in our environments.
In one of them (not reproductible in all environments and in one of my environment, problem does not occur in all realms -I can reproduce it at least in the master realm-), when I add an Audience mapper to admin-cli-dedicated (path: /auth/admin/master/console/#/master/clients/{client-id}/clientScopes/dedicated), I set the "Included client audience" to "account" and save. While saving, I can see the PUT method from the REST API called with included.client.audience set in its payload.
If I refresh the page, the GET method to retrieve the configuration of the Audience mapper is called and the included.client.audience is still set in the JSON/HTTP response BUT it is not displayed!
After that, if I try to update the configuration of the mapper without updating the included audience, as included.client.audience is not displayed, the payload is sent in a PUT request without value in included.client.audience and so, it is removed from the mapper configuration.
Workaround:
As a workaround, we don't set account in included.client.audience but in included.custom.audience
Does anyone faced such an issue? Is it a known bug of the admin console? Has it been fixed?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Problem description:
We are using Keycloak 26.2.4 in our environments.
In one of them (not reproductible in all environments and in one of my environment, problem does not occur in all realms -I can reproduce it at least in the master realm-), when I add an Audience mapper to admin-cli-dedicated (path: /auth/admin/master/console/#/master/clients/{client-id}/clientScopes/dedicated), I set the "Included client audience" to "account" and save. While saving, I can see the PUT method from the REST API called with included.client.audience set in its payload.
If I refresh the page, the GET method to retrieve the configuration of the Audience mapper is called and the included.client.audience is still set in the JSON/HTTP response BUT it is not displayed!
After that, if I try to update the configuration of the mapper without updating the included audience, as included.client.audience is not displayed, the payload is sent in a PUT request without value in included.client.audience and so, it is removed from the mapper configuration.
Workaround:
As a workaround, we don't set account in included.client.audience but in included.custom.audience
Does anyone faced such an issue? Is it a known bug of the admin console? Has it been fixed?
Thanks for your help
All reactions