Demo SAML 2.0 signle signon and prefill

[WaldoSmeets2]

Hi,

I'd like to demo a scenario where users log into a website using their credentials, and then go to a LiveCycle Guide (most likely through a REST interface) and LC automatically recognizes the user and prefills the form with the user data. Goal is to do this single signon using SAML 2.0.

Being new to SAML and the likes, I am kind of lost where to start setting up something like this. From my understanding I need to set up a identity provider, a service provider, have a web app implementing those and then configure LiveCycle to do so?

Has anyone done this before, any recommendations on what solutions to install to get this up and running easily? I have been looking at leveraging Shibboleth, a Wordpress instance and a WP plugin to integrate with it as well. In this case users log into the Wordpress 'site', and then move to the LC form.

Would this be the right track, or is there something I can already leverage?

[Gary_Gilchrist]

While I am not sure about Guides, here is some related infotmation that may help you towards the answer:

- If your browser session is already authenticated to LC (i.e. you have an LC cookie) then a Flex application can actually invoke LC services with remoting and provide SSO with the existing logged on user identity.

- There has been work done in ES2 to allow SAML to work as a means of browser based authentication to LiveCycle and this can be extended also to Flex applications. You can read about it here: https://zerowing.corp.adobe.com/display/lc/SAML+Authentication+and+Flex+Apps

- It is likely that REST based invovation of a Service will also respect any existing LC user cookie in the Browser session since I know that aalready works for invocation of Services over SOAP.

Gary.

[chetanm_oct]

You may want to look at the connect recording that we did as a working demo of

the SAML feature for ES2.

It's hosted at

https://zerowing.corp.adobe.com/display/lc/User+Manager+ES2+Features+Demo

[Jonathan_Herbac]

And scheduled to be externally shown on blogs.adobe.com/security in a post on the morning of 3/26.