Repository navigation
How to have one single user database and multiple instances of Keycloak? #44426
|
We would like to expose multiple instances of Keycloak, each with its own authentication flows. Typically, one instance would force MFA while the other would not. In other words, we would like to use those Keycloak instances only as OpenID Connect Providers and not as a user storage...while having one Keycloak instance that acts as user storage only. I'm wondering if there is a way to achieve such a thing. User federation looked like the right way to handle this but I can't find a way to make it work - actually there is no option to use a Keycloak instance as User Storage Provider. Is it even possible? |
Replies: 1 comment 2 replies
|
If the users are the same, could you not use clients with per-client authentication flows defined? I'm not sure I understand the use-case properly. Regarding user federation, you can either use LDAP / AD to store user data, instead of Keycloak's database (note that the database would still store some user information, such as 2FA tokens, required actions and some user attributes), or you could use one Keycloak instance as a (maybe generic) identity provider for the other(s). |
If the users are the same, could you not use clients with per-client authentication flows defined? I'm not sure I understand the use-case properly.
Regarding user federation, you can either use LDAP / AD to store user data, instead of Keycloak's database (note that the database would still store some user information, such as 2FA tokens, required actions and some user attributes), or you could use one Keycloak instance as a (maybe generic) identity provider for the other(s).