Domain discovery with login initiated in zitadel
Hello,
I'm not sure what I'm attempting to do is supported out of the box so before I spend more time I just wanted to check here to see if this model is supported.
Basically, I'm trying to build out a self-hosted multi-tenant application where each tenant is represented by a separate application instance and using Zitadel to authenticate users for each instance of that application.
I've enabled domain discovery and followed the steps outlined here: https://zitadel.com/docs/guides/solution-scenarios/domain-discovery which pretty much matches the desired configuration.
However, what I cannot seem to find any confirmation on is where does the user start when authenticating? All the examples I've seen the user is assumed to have begun their journey at the application instance (eg: alpha.company.com) before being redirected to login.company.com and then sent back to the application (I have this flow working fine, btw).
What I want to do is allow the user initially start at login.company.com without having initially visited alpha.company.com and then after authenticating be redirected to alpha.company.com. This is particularly relevant in the context of mobile apps where the same mobile app must be shared amongst all the tenants and the user can't reasonably be expected to enter their tenant domain into the app settings.
This is the same process Atlassian uses for JIRA, for example. I can start at www.atlassian.com, click "Sign in", login, and I'm subsequently redirected to my dedicated JIRA instance.
I've scoured the docs and cannot find any references to such a flow. I'm guessing I may have to look at building a custom hosted login UI to support this, but before I go down that road, is there a recommended way to implement this flow?
For reference, I'm working with a self-hosted instance v2.66.4.
I'm not sure what I'm attempting to do is supported out of the box so before I spend more time I just wanted to check here to see if this model is supported.
Basically, I'm trying to build out a self-hosted multi-tenant application where each tenant is represented by a separate application instance and using Zitadel to authenticate users for each instance of that application.
I've enabled domain discovery and followed the steps outlined here: https://zitadel.com/docs/guides/solution-scenarios/domain-discovery which pretty much matches the desired configuration.
However, what I cannot seem to find any confirmation on is where does the user start when authenticating? All the examples I've seen the user is assumed to have begun their journey at the application instance (eg: alpha.company.com) before being redirected to login.company.com and then sent back to the application (I have this flow working fine, btw).
What I want to do is allow the user initially start at login.company.com without having initially visited alpha.company.com and then after authenticating be redirected to alpha.company.com. This is particularly relevant in the context of mobile apps where the same mobile app must be shared amongst all the tenants and the user can't reasonably be expected to enter their tenant domain into the app settings.
This is the same process Atlassian uses for JIRA, for example. I can start at www.atlassian.com, click "Sign in", login, and I'm subsequently redirected to my dedicated JIRA instance.
I've scoured the docs and cannot find any references to such a flow. I'm guessing I may have to look at building a custom hosted login UI to support this, but before I go down that road, is there a recommended way to implement this flow?
For reference, I'm working with a self-hosted instance v2.66.4.
This guide should explain how domain discovery works and how to configure it in ZITADEL.
