On 09/01/13 3:46 AM, Sven Van Caekenberghe wrote:
Basically you should be able to get all the bits (preferably in Pharo 2.0) by
doing
(ConfigurationOfZincHTTPComponents project version: '2.2') load: 'SSO'
This does not load the Seaside demo code. I eventually figured that out.
I was able to get the Seaside demo running in Pharo-1.4.
Although the code is not yet production quality, we could use some feedback
from early adopters to help use shake out remaining problems.
I've used Cloudfork-SSO before, so trying out Zinc-SSO went quite
smoothly for me. The flow is much better with Zinc-SSO: the user is sent
directly to the application's next step, if they're already logged in -
unlike Cloudfork-SSO (where they were always sent to the identity
provider, even if already logged in there).
The clear separation of Seaside code is very helpful.
I had to poke around a bit to get stuff running, but I'm sure the doc's
will eventually make it clear what has to be done.
I've not tried the OAuth2 stuff yet, since I've not set up the necessary
application keys with Google/Facebook/Microsoft.
PS: We would like to thank Andy Burnett of Knowinnovation Inc and ESUG for
sponsoring this open source work.
My thanks too.
