I’m not 100% sure on this, but if you don’t’ care about users of your app receiving a SSO
token, I believe you can just do a direct access grant token and have them logged into
only the client your app using.
--
Christopher Savory
www.edlogics.com <
http://www.edlogics.com/>
<
http://www.edlogics.com/>
<
https://www.linkedin.com/company/edlogics> <
https://twitter.com/EdLogics>
On 4/3/17, 2:14 AM, "keycloak-user-bounces(a)lists.jboss.org on behalf of matteo
restelli" <keycloak-user-bounces(a)lists.jboss.org on behalf of
teoreste(a)gmail.com> wrote:
Hi all,
has anyone solved this problem?
Thank you,
Matteo
2017-03-27 17:37 GMT+02:00 matteo restelli <teoreste(a)gmail.com>:
Hi all,
we're planning to use Keycloak for a project and we're really excited
about that. The only thing that makes us thinking a little bit is the
authentication flow via native mobile app. I've already read that the
authentication via Webview or External Browser, using the Keycloak login
page, is the best practice. But we think that our mobile app designers
might prefer a native login form with some buttons for social login. How
can we do that?
1) For "direct" authentication via username & password we can use the
direct access grants mode, is it right?
2) What about the social login part? How can we authenticate users when we
receive the access token from an external identity providers such as
Facebook? We need to implement our custom Authenticators and then deploy
them with Keycloak?
I apologize because i know that this question has been asked a lot of
times, but we haven't been able to figure it out.
Thank you very much, have a nice day,
Matteo
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user