Access Zitadel using different URL for server-to-server as compared to from browser
š¬Self-hostedāQuestionā
Solved
Hello
We have integrated Zitadel into our product as our authentication provider for our Next.js application in a self-hosted manner.
Today, we have made sure that the NEXT.js server application reaches the Zitadel instance using the same DNS name as the end-users' browsers will. Unfortunately, with docker, this has meant that we use a less than optimal configuration there.
So my question is:
Does Zitadel support a configuration where the code that runs in the browser uses one DNS name to talk to Zitadel, and the code that runs server-side uses another?
Specifically, I would like the NEXT.js server components to talk to Zitadel using its internal docker DNS name, while the browser uses the external public DNS name of the host (Or a load balancer where relevant).
Is this doable?
We have integrated Zitadel into our product as our authentication provider for our Next.js application in a self-hosted manner.
Today, we have made sure that the NEXT.js server application reaches the Zitadel instance using the same DNS name as the end-users' browsers will. Unfortunately, with docker, this has meant that we use a less than optimal configuration there.
So my question is:
Does Zitadel support a configuration where the code that runs in the browser uses one DNS name to talk to Zitadel, and the code that runs server-side uses another?
Specifically, I would like the NEXT.js server components to talk to Zitadel using its internal docker DNS name, while the browser uses the external public DNS name of the host (Or a load balancer where relevant).
Is this doable?
