Hi,
Same scenario for me but with spring as backend and I use two separates
realm clients:
- the website client is "public" to allow login + page management by using
the user's realm role
- the backend client is "confidential" with resources
authorization/management
From the app, accessing a protected resource is a 3 steps process :
try to
access to the protected resources with the token obtained during login, if
denied by the backend, using the returned WWW-Authenticate header to get an
updated access token from the authorization service, access the protected
resource with the new token.
I guess it is not possible to get a better conf if you need a fine grained
authz
--
View this message in context:
http://keycloak-user.88327.x6.nabble.com/keycloak-user-JAX-RS-Backend-Ser...
Sent from the keycloak-user mailing list archive at
Nabble.com.