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
Assign Service Account Role${SUPER_USER_ROLE:-root} to Client ${RS_CLIENT_ID:-dcm4chee-arc-rs} by initial Keycloak configuration to enable to invoke RESTful services with access token dedicated to this client retrieved by OAuth2 Client Credentials Grant.
Before #4318, it was sufficient to assign ${AUTH_USER_ROLE:-user} as Service Account Role to Client ${RS_CLIENT_ID:-dcm4chee-arc-rs} to ensure such behavior, because
gunterze
changed the title
Assign _Service Account Role_ ${ROOT_USER_ROLE} to Client ${RS_CLIENT_ID} by initial Keycloak configuration
Assign Service Account Role ${ROOT_USER_ROLE} to Client ${RS_CLIENT_ID} by initial Keycloak configuration
Jan 5, 2024
gunterze
changed the title
Assign Service Account Role ${ROOT_USER_ROLE} to Client ${RS_CLIENT_ID} by initial Keycloak configuration
Assign Service Account Role ${SUPER_USER_ROLE} to Client ${RS_CLIENT_ID} by initial Keycloak configuration
Jan 5, 2024
gunterze
added a commit
to dcm4che-dockerfiles/keycloak-quarkus
that referenced
this issue
Jan 5, 2024
Assign Service Account Role
${SUPER_USER_ROLE:-root}
to Client${RS_CLIENT_ID:-dcm4chee-arc-rs}
by initial Keycloak configuration to enable to invoke RESTful services with access token dedicated to this client retrieved by OAuth2 Client Credentials Grant.Before #4318, it was sufficient to assign
${AUTH_USER_ROLE:-user}
as Service Account Role to Client${RS_CLIENT_ID:-dcm4chee-arc-rs}
to ensure such behavior, becauseArchive Network AE Attribute :
(dcmAcceptedUserRole)
was configured as
${AUTH_USER_ROLE:-user}
${ADMIN_USER_ROLE:-admin}
now:
${REGULAR_USER_ROLE:-user}
${ADMIN_USER_ROLE:-admin}
The text was updated successfully, but these errors were encountered: