Replies: 2 comments 5 replies
-
Hi @rafpor75 This is most likely due to the authentication service not being able to update the user information after login completion. After login completes it tries to contact the CRUD Service, thus mat be failing due to Rönd not knowing the API. You should be able to confirm this by looking at the logs of the authn-service and the rbac-container within the crud-service pod. If that's the case you have to define the desired API and open them with a proper policy, by using the Manual Routes and Policies tabs in the Authorization section. Please remember that once you enable Rönd on a microservice it will block all the incoming requests for which there is no known route. |
Beta Was this translation helpful? Give feedback.
-
thank you |
Beta Was this translation helpful? Give feedback.
-
Description
What product are you having troubles with?
ROND
What Console version are you using?
Console
Version: 1.93.1
Hi,
I’m successfully running Keycloak authentication using the authentication service.
However, when I enable Authorization (ROND service) on the CRUD service, authentication fails.
I noticed that the /token request is missing a cookie and results in a 500 Internal Server Error, followed by a /authorize request that fails with a 400 Bad Request.
In the logs of the authentication service, there is a 401 error on the /userinfo endpoint.
Thank you
Raffaele
Beta Was this translation helpful? Give feedback.
All reactions