Are you running CAS over HTTPS or HTTP? If you're running over HTTP, then you won't get SSO.
-Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Tue, Dec 16, 2008 at 9:18 AM, Iikku Mattila <[email protected]>wrote: > Hi, > I have a (seemingly) working CAS installation with > BindLdapAuthenticationHandler, setup like > http://www.ja-sig.org/wiki/display/CASUM/LDAP . I CASified Confluence > and Jira with Soulwing as per instructions on > http://soulwing.org/confluence-cas.jsp and > http://soulwing.org/jira-cas.jsp . When user logs on to either of those > apps, he's redirected to CAS login screen, he logs on successfully and > is redirected to the app. So all is okay with both individual > applications. However, after the user has logged on to one of the apps > and tries to use the other, he is not logged in automatically via CAS, > but instead redirected to the CAS login screen, where he can login > normally with username/password. > > So there is no single sign on, but instead two individuals logins both > handled through CAS. I'd rather have the sso. Is there perhaps some kind > of a switch that I've missed? > > Thanks, > Iikku Mattila > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
