We only support one server name. You might need to write a custom authentication/validation filter for now to handle this.
I'd also encourage you to open a JIRA issue for an enhancement in which we can support multiple (but finite) server names and we'll use the host header as long as it matches one of the provided ones (otherwise we can use the first one in the list). [CAS Client devs, please let me know if this sounds crazy] On Fri, Mar 25, 2011 at 1:06 PM, Thomas FRANCART < [email protected]> wrote: > Hi > > I have a set of J2EE applications integrated with a CAS server, deployed in > JBoss (applications and cas server are deployed on the same server). Our > problem is that our applications are accessed through 2 different URLs : > > - internal users will use http://INTERNAL-server-name > - external users will use http://EXTERNAL-server-name > > How this is done and the exact configuration of these 2 accesses are beyond > my knowledge, but I think they use web-gate or something. So the > "server-name" and "casServerUrlPrefix" parameters that we setup for our CAS > clients (either in JNDI or web.xml init-params) will fail for one of the > user profiles (if we set them to http://INTERNAL-server-name, the external > users will not be able to be redirected properly to the CAS server) > > I hope my explanations are clear... How can we handle this situation ? > Thanks > Thomas > > -- > *Thomas Francart* > *CTO** - Mondeca* > 3, cité Nollez 75018 Paris France > Tel. +33 (0)1 44 92 35 04 - fax +33 (0)1 44 92 02 59 > Web: www.mondeca.com > Blog : Leçons de choses <http://mondeca.wordpress.com> > > > -- > You are currently subscribed to [email protected] as: > [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
