CAS returns whatever NetId you've told it to resolve to. Its up to your application to be able to figure out who that is beyond there. As for Single Sign Out, CAS supports any sessions that are maintained on the server side (even if a cookie is used to identify it on the client side).
-Scott On Tue, Mar 11, 2008 at 5:15 AM, Teggo Lam <[EMAIL PROTECTED]> wrote: > > Thanks Scott, but now I have another ERROR: > > com.liferay.portal.NoSuchUserException: No User exists with the primary > key 0 > com.liferay.portal.NoSuchUserException: No User exists with the primary > key 0 > at > com.liferay.portal.service.persistence.UserPersistenceImpl.findByPrimaryKey > (UserPersistenceImpl.java:228) > ***************************************** > > I think that the problem is on the key provided by CAS server to Liferay > after authenticating user?!! > > I have an other question about the document above " > http://www.ja-sig.org/wiki/display/CASUM/Single+Sign+Out"; > > Could you tell me what would you mean by : > Where Single Sign Out Doesn't Work Does it mean that we can not configure > SSOut when the session management consists of cookies??? > > I tell you this because I use Liferay and its session management consists > of cookies!!!! > > > Thanks for reply and Sorry for my bad English > > > > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > > -- -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
