Closed ruromero closed 3 years ago
Hi @ruromero ! I've reproduced configuration and I am facing the same issue. Currently investigating...
Hi @ruromero !
I fixed it by adding the/auth
suffix in Keycloak privateUrl
=> http://keycloak-discovery.myproject.svc.cluster.local:8080/auth
.
I agree that it's hard to guess you've got the wrong URL. I'll add more information in logs.
Awesome, thanks @lbroudoux
For some reason I have not been able to provision the async feature connected to an external Kafka and an external Keycloak. It doesn't seem to work with an internal Keycloak either.
This is the configuration I used:
The microcks-serviceaccount client exists in the realm and seems to be similar to the one provisioned by microcks itself (which is failing at the same point).
When accessing the pod for debug I can manually retrieve the token:
I have also tried with the https://keycloak.myproject.svc.cluster.local:8443 but I guess the problem in that case is that it doesn't trust the self-signed certificate.
Any hints of what can be missing? Besides that would it be possible to add more information to this stacktrace about what the server is responding for better troubleshooting?
Thanks in advance