Zitadel OIDC discovery url not accessible when configured in route of APISIX gateway when both apps are in same cluster #7938
Unanswered
thirumurthis
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Can you share the full error you see in apisix? To me it looks like apisix does not use the host header in the call to zitadel correctly. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Deployed Zitadel and Apisix in kind cluster, and was able to access the UI's from the cluster.
The Zitadel is deployed to the cluster with
ExternalDomain
aszitadel.localhost
. The Apisix route configuration, OIDC plugin was configured with the discovery urlhttp://zitadel.localhost
, but Apisix pod is not able to access it within the kubernetes cluster.When I add the
http://<zitadel service>.<zitadel namespace>
in Apisix plugin notice the Zitadel discovery url is accessible, but Zitadel is not able to process since the domain name didn't match with ExternalDomain.Not sure if there is a way to add list of
ExternalDomain
which includeszitadel.localhost
and<zitadel service>.<zitadel namespace>
so zitadel can be accessible.refer Stackoverflow
Beta Was this translation helpful? Give feedback.
All reactions