CAS Client 2.1.1, also known
as Yale CAS Client, does not support SSOut. Your choices at this point
are:
- Add support to SSOut to
the Yale CAS Client
- Add support to SSOut to
webapp1
- Switch to use the
JA-SIG Java CAS Client, which supports SSOut, although this is not
guaranteed to work because it is unknown how webapp1 handles sessions.
Adam
Sunder Singh Negi wrote:
Hi All,
I have been using cas as a sso solution.
I am using CAS Server 3.2.1 and Cas client 2.1.1 and phpCAS 1.0.0.
I have a tomcat based webapp1 casified with the cas client and a phpCAS
casified webapp2.
I login to the webapp1 through CAS. It is working fine.
I login to webapp2 without the cas login. Since Single Sign On is
working fine.
Then in another tab in the same browser window i browsed to https://localhost:8443/cas/logout.
I access webapp2 it redirects me to cas login. Fine. As expected.
I expected the same for webapp1. But it didn't happen. I can access it
as if still login to to cas.
I viewed the cas log and found
sending logout request to http://localhost:8080/webapp1
sending logout request to http://localhost:8080/webapp2
I have phpCAS::handleLogoutRequests() in my webapp2 cas login script.
I wanted to know whether cas client 2.1.1 supports same feature.
Am i missing something.
My CAS filter for webapp1 is
<filter>
<filter-name>CAS Filter</filter-name>
<filter-class>edu.yale.its.tp.cas.client.filter.CASFilter</filter-class>
<init-param>
<param-name>edu.yale.its.tp.cas.client.filter.loginUrl</param-name>
<param-value>https://localhost:8443/cas/login</param-value>
</init-param>
<init-param>
<param-name>edu.yale.its.tp.cas.client.filter.validateUrl</param-name>
<param-value>https://localhost:8443/cas/serviceValidate</param-value>
</init-param>
<init-param>
<param-name>edu.yale.its.tp.cas.client.filter.serverName</param-name>
<param-value>localhost:8080</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>CAS Filter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
Cas login script for the webapp2 is
include_once('./CAS.php');
phpCAS::setDebug();
phpCAS::client(CAS_VERSION_2_0, "localhost", 8443, "/cas");
phpCAS::setNoCasServerValidation();
phpCAS::handleLogoutRequests(false,false);
phpCAS::forceAuthentication();
Please give some ideas on this.
Thanks
Sunder Singh Negi
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
|
begin:vcard
fn:Adam Rybicki
n:Rybicki;Adam
org:Unicon, Inc.;Professional Services
adr:Suite 113;;3140 North Arizona Avenue;Chandler;AZ;85225;United States
email;internet:[EMAIL PROTECTED]
tel;work:+1-480-558-2400
tel;home:+1-310-265-8286
tel;cell:+1-310-980-2758
x-mozilla-html:FALSE
url:http://www.unicon.net/
version:2.1
end:vcard
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
