Kenyee- >Quick question for you: can the federated SSO framework retrieve and >inject http cookies as part of user validation?
Kenyee, the JBoss SSO Framework does not dictate what type of authentication method is used by the web application. Examples being JAAS based modules, completely proprietary form based approach etc. The SSO Framework kicks in once an authentication is actually performed by the web application. Once that happens, the SSO Framework generates/injects the necessary secure SAML token as a domain cookie that will be passed around within the federation of websites, so that the user will not be asked to login when going to a partner site in that session. At this moment, this SSO token management is closely integrated with the JAAS based authentication approach. But, based on community feedback, I think I will be adding integration with non-JAAS based/proprietary authentication methods very soon by updating the LoginProvider interface. >1) a "remember me" checkbox next to the username/password field that >lets users hit that site for a while after logging in once The remember me cookie can be easily used by the web application to set the cookie on the browser and authenticate using whatever authentication mechanism the web application wishes. Once the authentication is completed successfully, the SSO Framework will kick in and perform the necessary SSO token management etc. Think of it as, the SSO Framework hooks on top of your web application. But, you don't need to change the authentication usecase of your web application like remember me cookies, etc. Just to clarify, the LoginProvider is an abstraction to Identity Stores that should be used by your authentication mechanism to pull Identity data from the store in a Store agnostic manner (LDAP, SiteMinder, JDBC etc). I have gotten community feedback that besides the username, and password parameters, there needs to be provision for sending in more information as criteria to perform a successful login. This will be addressed so that the LoginProvider interface can be made more generic >2) another web server on the same domain that puts in a session cookie >of a logged in user (i.e., you log into that web server, the cookie is >generated for your domain, then you go to the jboss federated server >and autologin) What you are referring here it seems is a session cookie for a logged in user for that web application. This is perfectly fine and is independent of the SSO token that is generated to perform autologin via the Federation Server. The Federation Server does not process any proprietary app server specific login sessions. It uses the SAML token to perform the single sign on which is generated by the SSO framework when a user successfully authenticates on a partner web application. For some clarifications on some of the SSO architecture questions, also look at the following forum thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=93785 I hope this answers your questions. Thanks Sohil View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983554#3983554 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983554 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
