-
Notifications
You must be signed in to change notification settings - Fork 29
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
[Bug] Local network communications #276
Comments
I am not fully sure I can follow 😁 so let me try and ask some questions.
|
It works, but we want to close it to the test environment behind an IP whitelist using WAF.
It used to return an error, but now it doesn't, because I'm substituting the Host header at the sidecar (istio) level. By doing so, I just bypassed the zitadel check to try to use the service entirely inside the Kubernetes network. The problem is that by closing the zitadel service behind CF, my service's integration with the zitadel service breaks. And this is despite the fact that zitadel's GPRC address is listed as local (service name in kubernetes)! |
Hi @roquie, did you find a workaround? I'm having the same issue |
No. @fforootd any updates? |
ok so I managed to do it by creating my own (and probably not very good solution)
and passing it to the client
|
I want to do a simple thing. Close my development environment behind Cloudflare so no one can access, including the Zitadel test instance. But here's the trouble, by closing IP access to WAF I get 403 errors in the logs of my service which is integrated with Zitadel via this SDK.
In order to be able to use Zitadel within the local network (Kubernetes), I wrote a local GRPC endpoint address for the Zitadel service and at the Istio level, in sidecar, made a host replacement (to pass the security check).
This allowed the
zitadel:80/.well-known/openid-configuration
endpoint to converge successfully, similarly configured h2c app protocol in Kubernetes Service. Everything is done, for successful local operation.My settings for the go-client:
issuer: https://sso.example.com
grpc_endpoint: zitadel:80
option: WithInsecure()
Log when trying to get a user profile:
Now the question is why it ignores the local grpc endpoint and uses
issuer
to perform the request?The text was updated successfully, but these errors were encountered: