Most CAS clients allow you to specify the URL in one of two ways: 1. provide a hard-coded "serviceurl" which will not vary. 2. Provide the start of a service url (i.e. https://my.application.com) and then have the client generate the rest based on the current request.
It seems like you want to be using #2. Cheers, Scott On Tue, Jan 18, 2011 at 3:40 AM, Serouche Rahimpour <[email protected]>wrote: > dear list, > > I have 2 URL which are sending the request to my CAS server. > they are basically in the form > http://%{my context}/<my URL>/ > > Sometimes I need to send something like this > http://%{my context}/<my URL>/?<some variables - actually only one> > > In the Tomcat log I see > " ... temporary moved ..." > > So it looks like Tomcat moves the URL aside, sends the authentication > request to the CAS server. This later answers back, "Ok here is your ticket" > > Tomcat opens the serviceUrl and my variable is lost > > Could anybody help on to solve this problem? > > I checked the archives and didn't find anything relevant to my issue. > > Any tips would be appreciated. > > > > > -- > --------------------------------------------------------------------- > Serouche Rahimpour > European Southern Observatory ~~ http://www.eso.org > > + O > O + OTS/CAS | Office 3001 > + E S Tel.:+49-89-32006-673 > O + Fax.:+49-89-32006-677 > O + O > O + > O > > > -- > 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
