ZITADEL was already on my list to try in the next round.
Can you clarify the pricing / plan required for that feature set?
There's some more info on our multi-tenancy data model here (https://stytch.com/docs/b2b/guides/multi-tenancy), and here's the PUT request you'd use to manage any of those org configurations: https://stytch.com/docs/b2b/api/update-organization
I’m highly considering bringing auth in house with Keycloak. I’ve run it in the past at previous companies so am familiar with it, but it’s going to be an extra thing to maintain due to self hosting, their themeing also is not great. However this is pretty much an end all solution that doesn’t really get expensive over time as our user base grows.
Wondering if folks have any advice?
I’m the founder. Would love to hear your feedback and happy to answer questions.
I’ll kick the tyres in my next round of investigation though to see how it looks.
(Disclaimer, I am founder and CTO of authentik)
Pricing wise this is available on the Scale tier currently dubbed as "Enterprise SSO" although "B2B Organizations" probably would be more correct: https://www.ory.sh/pricing/
There are no limits to how many organizations you can have.
Regarding MFA - the MFA enforcement typically is the responsibility of the IDP the company owns. So for example dean@companyA.com use Okta and they enforce 2FA for their users. anna@companyB.com use OneLogin and they do not enforce MFA.
In terms of other enforcement, I meant more wrt to an organisation that _didn't_ use another IDP but still wanted to apply PW policies (for example) on their domain.
Could you create an Ory project (sorry, don't know all your terminology) to forward on to?
Something like:
Our app -> Ory -> split by domain -> Ory for specific domain -> Policies.
So you want a screen in front of the login process where someone enters their email address, and then a second screen where a variety of login options are presented?
Along with the ability to enforce MFA on a per domain basis?
Anything else you are looking to customize at the domain level, such as password rules or registration ability?
Other than that I'd suggest putting a page in front of our login pages with the domain logic, and modeling each set of emails as either an application, organization or tenant, depending on the specific features you need.
Either way, hope you find the right solution for your needs!
Just our app that needs logging in to and would like to allow the usual things (password, social etc) but also allow customising the rules per email domain.
For example, if someone enters someone@example.com in to the login form they'll be shuffled off to this Azure connection for authentication. Or maybe they use our login pages, but MFA is enforced.
Things that I've tried (eg Authentik and FusionAuth) weren't well suited for per organisation controls.