Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AuthN-AuthZ with Keycloak is not fully accessible via Kind Cluster environment locally #247

Open
hteeyeoh opened this issue Aug 1, 2024 · 0 comments
Labels

Comments

@hteeyeoh
Copy link

hteeyeoh commented Aug 1, 2024

The authentication and authorization via JWT tokens generated by Keycloak using Kind Cluster is not working in local host.
Token fetching and curl command only able to work inside the kind container. This is because of the port exposing for kind cluster setup is much more complicated.
To make token fetching and curl command working in kind container, a w/a is needed:

  1. set env proxy: HTTP_PROXY, HTTPS_PROXY, NO_PROXY
  2. export KEYCLOAK_ADDR=<kind_container_ip>: <keycloak_node port>
  3. export INGRESS_HOST=127.0.0.1
  4. export INGRESS_PORT==
    $(kubectl -n "${INGRESS_NS}" get service "${INGRESS_NAME}" -o jsonpath='{.spec.ports[?(@.name=="http2")
    ].nodePort}'
  5. Then perform token fetching and curl command in the container via "docker exec -it <kind_container_name> bash " command

This is for tracking purpose. As it is related to Kind Cluster infrastructure limitation not the Auth module here.

@daisy-ycguo daisy-ycguo added the gmc label Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants