CASFilter configuration and environment-specific artifacts

[David Whitehurst]

Mark:

You have to modify your web.xml for each deployment hosting.  While
this may seem cumbersome, it's very important. Your CAS filter makes a
second and totally separate request to it's CAS server and this
request basically says, "here's this ticket thingy and I guess I'm
asking you to verify some user's credentials".  The web.xml
specification is as important and DNS that hasn't been highjacked,
i.e. it's how the application owner knows that CAS has protected it's
user requests.

Hope that helps,

David

On 10/9/08, McEahern, Mark S <mceahems at mail.slh.wisc.edu> wrote:
> Hi, it looks like the CASFilter configuration requires that I place
> environment-specific artifacts into my web.xml (which is then packed
> into my .war).
>
> http://www.ja-sig.org/wiki/display/CASC/Using+CASFilter
>
> That is, I need to set one of the following:
>
>  edu.yale.its.tp.cas.client.filter.serverName
>  edu.yale.its.tp.cas.client.filter.serviceUrl
>
> How do I then take my .war and drop it into successive environments
> (dev, test, ultimately prod) without having to edit web.xml with
> environment-specific differences?
>
> How have others addressed this issue?
>
> Thanks,
>
>
>
> Mark McEahern
> Lead Architect
> Division of Public Health Informatics and Surveillance
> Wisconsin State Lab of Hygiene
>
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>