apupier commented on code in PR #29780: URL: https://github.com/apache/camel/pull/29780#discussion_r4597033073
########## docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_24.adoc: ########## @@ -302,6 +302,15 @@ The camel-sjms and camel-sjms2 consumers now map a received `jakarta.jms.StreamM bytes, as the camel-jms consumer does, so a body sent with `jmsMessageType=Stream` arrives as the bytes that were sent. Before, the body was the `jakarta.jms.StreamMessage` itself. To get the JMS message, use `mapJmsMessage=false`. +=== camel-keycloak - Keycloak 26.8.2 requires the kc-admin-api client scope + +This is a change in Keycloak, not in Camel: from Keycloak 26.8.2 the Admin REST API accepts only access tokens that +carry the built-in `kc-admin-api` client scope, and rejects other tokens with `401 Unauthorized`. The Keycloak upgrade +assigns the scope to `admin-cli` and `security-admin-console` only. When the `keycloak` producer authenticates with +`clientId` and `clientSecret` of your own client, assign `kc-admin-api` to that client as a default client scope; a +pre-obtained `accessToken` must be issued with that scope too. Username and password authentication uses `admin-cli` +and keeps working. The integration tests of camel-keycloak now run against Keycloak 26.8.2. Review Comment: this is not true for ppc64le ########## docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_24.adoc: ########## @@ -302,6 +302,15 @@ The camel-sjms and camel-sjms2 consumers now map a received `jakarta.jms.StreamM bytes, as the camel-jms consumer does, so a body sent with `jmsMessageType=Stream` arrives as the bytes that were sent. Before, the body was the `jakarta.jms.StreamMessage` itself. To get the JMS message, use `mapJmsMessage=false`. +=== camel-keycloak - Keycloak 26.8.2 requires the kc-admin-api client scope + +This is a change in Keycloak, not in Camel: from Keycloak 26.8.2 the Admin REST API accepts only access tokens that +carry the built-in `kc-admin-api` client scope, and rejects other tokens with `401 Unauthorized`. The Keycloak upgrade +assigns the scope to `admin-cli` and `security-admin-console` only. When the `keycloak` producer authenticates with +`clientId` and `clientSecret` of your own client, assign `kc-admin-api` to that client as a default client scope; a +pre-obtained `accessToken` must be issued with that scope too. Username and password authentication uses `admin-cli` +and keeps working. The integration tests of camel-keycloak now run against Keycloak 26.8.2. Review Comment: this is not the case for ppc64le -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
