Repository navigation
Replies: 2 comments 4 replies
|
More than likely you have not configured proxy-headers on the keycloak server, so you are failing CORS checks and / or requests are being seen as from an insecure context. |
4 replies
|
Issue solved. For reference here's my working values.yaml (for helm chart bitnami/keycloak): |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Before reporting an issue
Area
No response
Describe the bug
I configured K8s with Istio Gateway ingress controller.
For deployment of keycloak I'm using bitnami helm chart.
Istio gateway is configured with SSL Termination.
And here's the virtual service manifest:
If I create port-forward to localhost with
kubectl port-forward svc/keycloak -n keycloak 8080:80admin console UI loads w/o any problem.Version
26.2.4
Regression
Expected behavior
Admin console with login
Actual behavior
How to Reproduce?
Enter (pretty) URL in any browser.
Anything else?
No response
All reactions