Thank you Marek

To check that I understand this approach correctly, is the following a correct summary of how a federation provider works?

existing user tries to login via Keycloak
Keycloak checks if the user exists in the keycloak IDM. If user is not there then use federation provider
the provider will get the user by email address or username, and return the User object.
This user object can then be mapped and saved into keycloak.
Next time user tries to login user is retrieved from keycloak idm

Question - where is the federated provider deployed? Is it in our app, or installed into Keycloak? Or something else?

Thanks

On Thu, Mar 19, 2015 at 8:03 PM, Marek Posolda <mposolda@redhat.com> wrote:

Hi,

it will be best if you write custom FederationProvider and point it to your database. See http://docs.jboss.org/keycloak/docs/1.1.0.Final/userguide/html/user_federation.html and examples in appliance-dist (Subdirectory examples/providers)

Marek

On 19.3.2015 19:58, Anton Hughes wrote:
Hello

Im currently investigating using Keycloak as a solution to manage users, as well as authentication and authorization.

Currently, we have a jboss Errai application, and have a relational database of users and their encrypted password.

Is there any tutorials, or advice, on how we would migrate our users to the Keycloak IDM?

Thanks and regards

Anton
_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user

--

Anton Hughes

Co-founder
ah@magick.nu
www.magick.nu