Re: [keycloak-user] Keycloak and registration workflow for REST API platform
To answer your question properly I'd need more details about what you're trying to
achieve.
It does sound like we pretty much already have what you need, with the exception of
letting users themselves create clients. Depending on your use case it may be a good idea
to have a single realm (and share users) between all developers/applications, or it may be
better to have a realm per developer/application.
For the latter we do have a role that lets users create new realms, but not use any other
realms. This could be used to let a developer register with your platform and then be able
to login to the admin console to create clients, users, or whatever they want. For the
first we have discussed in the past, but do not support it yet, the ability to let users
register clients through the account management console.
----- Original Message -----
From: "Christina Lau" <christinalau28(a)icloud.com>
To: keycloak-user(a)lists.jboss.org
Sent: Tuesday, 8 July, 2014 4:34:57 PM
Subject: [keycloak-user] Keycloak and registration workflow for REST API platform
I am wondering if I can use Keycloak to implementation the registration
workflow for a REST API platform, similar to Twitter
(https://apps.twitter.com/) or Linkedln
(https://developer.linkedin.com/rest).
I found some features like social login very applicable. However I am not
quite sure how I will model this in Keycloak. For example, will I have 1
realm per user and each user that registers will have their own oauth client
for their third party appl(s) that I need to grant access to similar to the
Tutorial 3 demo?
If this is feasible to implement, can you outline the steps involved in this
use case. I am thinking I will need to build a lot of it using the REST APIs
you provided. Thanks in advance for any help.
Christina
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user