RHi @Marcel van den Berg thanks for your question 
, I will get back to you with more findings that will help you setup the multi org IDP
, I will get back to you with more findings that will help you setup the multi org IDPRHi @Marcel van den Berg aplogies that it took so long to get back but I wa reading/researching more about your scenario, and I guess your problem could be fixed by Enabling Domain Discovery.
Follow the Domain Discovery Guide to ensure the flow is optimized for email-based org detection.
the way it works is(in short)
:
Users enter their email (e.g., user@company.com)
Zitadel routes them to the company.com org’s login policy The IDP button should now appear alongside the password field.
please give it a read and see if it helps, and feel free to ask any followup, I can dig more into it later
Follow the Domain Discovery Guide to ensure the flow is optimized for email-based org detection.
the way it works is(in short)
:Users enter their email (e.g., user@company.com)
Zitadel routes them to the company.com org’s login policy The IDP button should now appear alongside the password field.please give it a read and see if it helps, and feel free to ask any followup, I can dig more into it later
JHi @Rajat what would you recommend if we have the need to have the same domain in different organizations though? Example: user1@company.com in Organization Company-Tech and user2@company.com in Organization Company-Sales (just an example)
Rhi @JC I think what you can try in that case is instead of user1@company.com and user2@company.com, use the following:
user1@tech.company.com for Company-Tech
user2@sales.company.com for Company-Sales.
The you can verify those sub domains(here's how you can do it), something like tech.company.com and sales.company.com in their respective orgs.
And then Zitadel will route users based on their email's subdomain.
This is what I could come up with based on the situation you presented
user1@tech.company.com for Company-Tech
user2@sales.company.com for Company-Sales.
The you can verify those sub domains(here's how you can do it), something like tech.company.com and sales.company.com in their respective orgs.
And then Zitadel will route users based on their email's subdomain.
This is what I could come up with based on the situation you presented
JHi @Rajat I saw theres's an issue that would address my needs (https://github.com/zitadel/zitadel/issues/9535). Cheers!
GitHub
ZITADEL - Identity infrastructure, simplified for you. - Issues · zitadel/zitadel