Re: [keycloak-dev] Pulling stuff from IdentityBroker and next steps....
What I'd really like to do is to get the protocol and flows working
before focusing on the admin UI and REST interface for it. I have SSO
login working. Working on Single Log Out today. Then OAuth grants.
I'm working from a demo under /examples/as7-eap6. It requires you to
install Resteasy 3.0.2 on top of EAP 6.1, then run mvn jboss-as:deploy.
I'm committing and merging every time I get something new working.
If I can get logout, and OAuth finished by Monday, we can have a hangout
to discuss how we can fit Social into this flow. Hopefully after the
meeting you can focus on getting social to work and I can then work on
the backend some more to get it working with the latest Picketlink that
was released today.
On 7/26/2013 9:37 AM, Stian Thorgersen wrote:
So that completes the pulling stuff from IdentityBroker task.. Now we
need to look at how to integrate the pieces.
UI
--
For UI there's a dummy REST resource (org.keycloak.ui.example.Admin) that we could
use as a starting point for defining the real admin REST endpoints for Keycloak.
Social
------
Needs to be able to:
* Retrieve information about the application (realm, provider key, provider secret,
etc.)
* Get/save/update users in IDM
* Login and redirect back to application
HTML SDK
--------
We didn't really get much value from IdentityBroker here. As you've suggested it
would probably be safest to use a server-side solution for the login/registration forms.
It would be good to have a Hangout early next week to discuss the next steps. In the mean
time I can have a look at improving the login/registration forms.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com