[keycloak-user] Customization of authentication mechanism and +

[Stian Thorgersen]

We don't currently have a way to plugin your own authentication mechanism, but this is something we'll be adding.

You have two choices when it comes to users, you can either use our user federation provider mechanism to sync between Keycloak and your current db. Or you can migrate the users fully to the Keycloak db. In either case you have an option on overriding how passwords are verified (either UserFederationProvider or by extending an existing UserProvider). With the above authentication mechanism we'll most likely also make the verification of passwords pluggable which would support different hash algorithms.

----- Original Message -----
> From: "Kalinga Dissanayake" <kalinga at leapset.com>
> To: keycloak-user at lists.jboss.org
> Sent: Monday, March 16, 2015 10:48:55 AM
> Subject: [keycloak-user] Customization of authentication mechanism and +
> 
> 
> 
> Guys,
> 
> I need to understand the capability of keycloak with my requirement and to
> ensure that keycloak is scalable to meet my needs. My main requirement is to
> integrate keycloak to our system to support SSO hence I need to migrate my
> existing users. My main concerns;
> 
> 
> 
> 1/ Customize authentication method.
> 
> I need to authenticate users similar to what we currently use in our
> production system. In our system, users are identified by username, password
> and the pin.
> 
> For instance;
> 
> User -> jack, password -> pwd, pin -> 50000
> 
> User should enter all three to login to the system.
> 
> I went through the codebase and I saw that the Authentication Manager (which
> is a concrete class) does all the work inside keycloak. I managed to
> customize the frontend with ease, however, in order to support the pin in
> the backend seems like I have to customize the AuthenticationManager class
> (no direct SPIs).
> 
> Although there is a link here;
> 
> http://docs.jboss.org/keycloak/docs/1.0-beta-3/userguide/html/authentication-spi.html
> 
> I cant seem to find anything here which matches the current code base (to via
> a new authentication method via spis) and the example has been removed.
> 
> 
> 
> 2/ Customize password hashes.
> 
> We have our own algorithm used to store password hashes. What should I do to
> add this to keycloak?
> 
> I do not know the current passwords of the users already in our system, so
> when doing the migration i need keyclock to support the current algorithm we
> use. Can we plugin new hashing algorithms to meet my needs?
> 
> 
> 
> Any other issues I might face?
> 
> I feel key cloak is the right choice if the above two questions are answered.
> Please let me know.
> 
> _______________________________________________
> keycloak-user mailing list
> keycloak-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-user