Alex:
Your ticket validation looks like version 1. The CAS 2 mechanics are
configured a little differently like this.
<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>http://myhost.mycompany.com/cas/login</param-value>
</init-param>
<init-param>
<param-name>edu.yale.its.tp.cas.client.filter.validateUrl</param-name>
<param-value>https://myhost.mycompany.com:8443/cas/serviceValidate</param-value>
</init-param>
<init-param>
<param-name>edu.yale.its.tp.cas.client.filter.serverName</param-name>
<param-value>myhost.mycompany.com</param-value>
</init-param>
<init-param>
<param-name>edu.yale.its.tp.cas.client.filter.wrapRequest</param-name>
<param-value>true</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>CAS Filter</filter-name>
<url-pattern>/ControllerServlet</url-pattern>
</filter-mapping>
<filter>
David
On 7/30/08, Alex Johnson <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Thank you for your quick answer. I want to ask a bit more about this. I want
> to know which CAS architecture ( CAS1 or CAS2) I am using in my setting.
>
> For "Hello World" application, the setting is exactly like the demo, and the
> web.xml is like below, the same as demo
>
> .....
>
> <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://compA:8443/cas/login</param-value>
</init-param>
<init-param>
<param-name>edu.yale.its.tp.cas.client.filter.validateUrl</param-name>
<param-value>https://compA:8443/cas/serviceValidate</param-value>
</init-param>
<init-param>
<param-name>edu.yale.its.tp.cas.client.filter.serverName</param-name>
<param-value>compA:8080</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>CAS
> Filter</filter-name>
<url-pattern>/servlet/HelloWorldExample</url-pattern>
</filter-mapping>
> .....
> For the application B, in web.xml, it's like below
>
> .....
> <filter>
> <filter-name>CAS Authentication Filter</filter-name>
>
> <filter-class>org.jasig.cas.client.authentication.AuthenticationFilter</filter-class>
> <init-param>
> <param-name>casServerLoginUrl</param-name>
> <param-value>https://compA:8443/cas/login</param-value>
> </init-param>
> <init-param>
> <param-name>service</param-name>
>
> <param-value>http://compA:8080/testme/test.jsp</param-value>
> </init-param>
> <init-param>
> <param-name>serverName</param-name>
> <param-value>compA:8080</param-value>
> </init-param>
> </filter>
>
> <filter>
> <filter-name>CAS Validation Filter</filter-name>
>
> <filter-class>org.jasig.cas.client.validation.Cas10TicketValidationFilter</filter-class>
> <init-param>
>
> <param-name>casUrlServerPrefix</param-name>
> <param-value>https://compA:8443/cas</param-value>
> </init-param>
> <init-param>
> <param-name>serverName</param-name>
> <param-value>compA:8080</param-value>
> </init-param>
> </filter>
>
> <filter>
> <filter-name>CAS HttpServletRequest Wrapper Filter</filter-name>
>
> <filter-class>org.jasig.cas.client.util.HttpServletRequestWrapperFilter</filter-class>
> </filter>
>
> <filter-mapping>
> <filter-name>CAS Authentication Filter</filter-name>
> <url-pattern>/*</url-pattern>
> </filter-mapping>
>
> <filter-mapping>
> <filter-name>CAS Validation Filter</filter-name>
> <url-pattern>/*</url-pattern>
> </filter-mapping>
>
> <filter-mapping>
> <filter-name>CAS HttpServletRequest Wrapper Filter</filter-name>
> <url-pattern>/*</url-pattern>
> </filter-mapping>
> ......
>
> So, based on above, am I using CAS 1 configuration or CAS 2 configuration
> for both applications-"Hello World" and B? Also, determine if using CAS 1
> or CAS 2, it's based on the setting in web.xml?
>
> If I am using CAS 1, how can I change above (web.xml) to become CAS 2?
>
> Sorry for all the silly questions.
>
> Thanks,
>
>
> Alex
>
>
>
> ________________________________
>
>
>
> Date: Wed, 30 Jul 2008 11:29:11 -0400
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED];
> [email protected]
> Subject: Re: CAS basic questions
>
>
>
> On Wed, Jul 30, 2008 at 11:02 AM, Alex Johnson <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am a newbie here. I follow the link
> http://www.ja-sig.org/wiki/display/CASUM/Demo
> to set up CAS on the following envirment.
>
> Windows XP
> Tomcat 5.5.23
> CAS client 2.1.1
> CAS 3.2.1
>
> my
> http://mymachinename:8080/servlets-examples/servlet/HelloWorldExample
> works. It is redirected to CAS login page. After I input login, it is
> redirected back to open "Hello World"
> Then I go a step forward to put another simple Java application (B) into
> Tomcat and pointed to the same CAS. It works too. I can open "Hello World"
> application and no need to login CAS again to open another application (B),
> or After I login into B, I don't need to login into CAS again for "Hello
> World" application
>
> My question is
>
> 1. After I make these work, am I in CAS 1 or CAS 2?
> Well you're running CAS 3.2.1 and utilizing either the CAS1 or CAS2
> protocol, depending on how you've configured your CAS client.
>
>
> 2. I am using CAS client 2.1.1 or CAS server 3.2.1, does it mean I am using
> CAS 2?
>
> Using CAS 3.2.1 you have the optional of three protocols: CAS1, CAS2, SAML
> 1.1. Since you're using the Yale CAS Client 2.1.1, you're only supporting
> CAS 1 or CAS2 on the client side. Which one you are using depends on your
> configuration. Both will work fine.
>
> -Scott
>
>
>
>
> Thanks,
>
>
> Alex
>
>
>
>
> _______________________________________________
> 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
>
>
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
