[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2508) openId support components

koen handekyn (JIRA) jira-events at lists.jboss.org
Tue Jan 29 13:48:59 EST 2008

    [ http://jira.jboss.com/jira/browse/JBSEAM-2508?page=comments#action_12397404 ] 
koen handekyn commented on JBSEAM-2508:

i have a working solution based on the openid4java library. the documentation still says it requires to update the XML libs but i haven't had any issues with the ones used standard in jboss422 and have been logging on from several openid providers.

the patch solution i brew is an adaptation of the demo servlet that comes with the library. iti puts an openidentity token in the session scope after successful authentication and than redirects to a login page with an action on it that triggers identity.isLoggedIn(true). my authenticate method checks the session state for the availlability of the openidentity token in the session. [ on first logon i move to a registration wizard to confirm some identity meta data that was reftreived through the openid standard ]

if you are really interested i could make a little application just demonstrating the openid authentication/registration.

but as said and as discussed on the forum, SSO doesn't match extremely well with the current seam security framework, so something cleaner should be aimed at.

> openId support components
> -------------------------
>                 Key: JBSEAM-2508
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2508
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Security
>            Reporter: koen handekyn
>            Priority: Optional
> provide standard components to allow easy setup for openId support in a seam application.
> the seam identity contains both username and password fields.
> an openId identity consist soly of an identity string.
> ideally an openId authenticator takes in just a single openId identity, performs the openId logn procedures and concludes (in case of succesful authentication in a logged in session, with the identifier confirmed.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list