On 21 Nov 2018, at 18:07, Lamina, Marco <marco.lamina(a)sap.com>
To answer your questions:
- I upgraded from 4.5.0 to 4.6.0
- Clicking on "Client Scopes" and "Evaluate", all scopes are shown as
- Even when I create a new client and add the scope, it is not added to the token
On 11/21/18, 5:19 AM, "Marek Posolda" <mposolda(a)redhat.com> wrote:
No, it doesn't need to be updated in any profile like Token Exchange.
Question is, from which version you upgraded? Note that during upgrade
to 4.0.0, the realm default client scopes are not automatically linked
to the clients. Thing is, that clients from previous version already has
some protocolMappers defined on them, so the clientScopes are not added
to it. You may need to do change your clients manually and remove
protocolMappers from them and link them to default client scopes.
Just the new clients, which you will create now through admin UI, will
have the client scopes added to them. See details in the docs:
BTV. When you're on client, you can click to "Client Scopes" and then
"Evaluate" to see what are applied client scopes and check what
clientScopes will be applied based on the value of "scope" parameter.
On 21/11/2018 01:55, Lamina, Marco wrote:
> I upgraded to 4.6.0 using the Kubernetes Helm chart. After the upgrade, token
exchange stopped working, which I was able to fix thanks to . Unfortunately, none of my
client scopes are working anymore. Trying to get a token using client credentials
succeeds, but anything I pass into the “scope” parameter is ignored and none of my default
client scopes are applied. The “scope” claim in the token endpoint response is always
> Is that a feature that needs to be enabled similar to the token exchange?
> keycloak-user mailing list
keycloak-user mailing list