Sorry, I wasn't clear enough. The problem we're having is with social logins
When we have to login a user via social links (Google or Facebook) we need
to send him to a webview, because Keycloak communicates with the social
networks via the default flows we already have implemented.
But from a mobile standpoint this could be improved, because the user can
alerady have a Google account and/or a Facebook account on his mobile
device. So that could be used instead of making the user login again on a
The idea is to send the social information we already have on the mobile
device to Keycloak and get a token in return (we can do this with
The ideal thing would be a SDK for this that would (for example) be
instantiated with URI and client_id, and would provide a method for login.
I know this might not be in your roadmap for any time soon, but I'd like to
know if you have thought about any of this.
This provides a very different user experience for the user, and I think
this feature would be appreciated by many.
Thank you all again!
On Wed, Nov 26, 2014 at 4:13 PM, Rodrigo Sasaki <rodrigopsasaki(a)gmail.com>
I was wondering if there is a plan (or maybe something already built) for
native mobile authentication with Keycloak.
Right now we need to redirect the user to a web view so he can interface
with Keycloak to login, and from there on he can use the app normally, but
is there something native for this? We're trying to find ways to use the
smartphone's native authentication systems to login the users, and so far
we haven't been able to make it work.
Have you thought of something along those lines?