On 3/14/2014 11:15 AM, Stian Thorgersen wrote:
----- Original Message -----
> From: "Bill Burke" <bburke(a)redhat.com>
> To: keycloak-dev(a)lists.jboss.org
> Sent: Friday, 14 March, 2014 2:12:20 PM
> Subject: Re: [keycloak-dev] LDAP integration
>
> Don't we need to have LDAP as a user store? Won't companies have a user
> LDAP store they want to point Keycloak to? If you have an Auth SPI
> only, then you'll still need to register the users with Keycloak.
The idea with the authentication would be similar to social login. On first login a user
would be created internally in Keycloak, and there would be a link to the user in LDAP. It
would provide us with something relatively simple without the fuzz. Social login requires
registration to be enabled for new users, but that shouldn't be required to create
users that "links" to an LDAP store.
We can even investigate allowing multiple authentication providers for a single realm.
For example if a user exist in Keycloak you can check if there is a LDAP link, if there is
authenticate with LDAP, otherwise with Keycloak. If no user exist, check with the other
configured authentication providers if one exists.
In the second round we can worry about syncing, or alternatively by using LDAP directly
for users/role-mappings. I'm not 100% convinced, but I believe the syncing approach is
the simpler and probably better solution to "federation".
So, all user updates (password, attributes, otp, etc...) will be stored
in Keycloak and then synced with LDAP?
Bill
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com