Dhairya-007 commented on PR #29955:
URL: https://github.com/apache/camel/pull/29955#issuecomment-6892564526

   All five done, thanks — the three notes were wrong as you and gnodet-bot 
describe.
   
   1. `PERMISSION_NAME`: now "createResourcePermission takes a 
ResourcePermissionRepresentation as the POJO request body, and the other 
permission operations identify the permission with CamelKeycloakPermissionId". 
`PolicyRepresentation` only shows up in `updatePermission` and 
`getPermissionById`, both keyed on `PERMISSION_ID`.
   2. `SCOPE_NAME`: now "there are no authorization-scope operations, and the 
client scope operations use CamelKeycloakClientScopeName" — the only 
`scopeName` read in the producer is from `CLIENT_SCOPE_NAME`.
   3. `CREDENTIAL_TYPE`: now "no credential operation takes a 
CredentialRepresentation request body. deleteUserCredential uses 
CamelKeycloakCredentialId, and resetUserPassword builds a password credential 
from CamelKeycloakUserPassword". `resetUserPassword` constructs the 
representation itself from `USER_PASSWORD`, and `getUserCredentials` only 
returns them.
   4. Added a `=== camel-keycloak` section to 
`camel-4x-upgrade-guide-4_24.adoc`, as a two-column table of all eleven headers 
and where each value belongs instead.
   5. The PR description now cites #29709.
   
   Regenerated the two `keycloak.json` files and the three header javadocs in 
`KeycloakEndpointBuilderFactory`.


-- 
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]

Reply via email to