The CAS serverName can be whatever you'd like it to be. The current version restricts it to one value though.
On Mon, Mar 1, 2010 at 11:57 AM, <chris_whit...@jbhunt.com> wrote: > > We have quite a few applications using DNS names instead of straight server > names so when we are looking at using CAS one thing we hit against was the > required server name that was being used to construct the serviceURL.... For > example Our Liferay portal has several communities that have virtual hosts > and when some one goes to one of them directly CAS would not work because > the servername + URI does not match the actual URL... > > We have figured a change that would allow us to continue but I'm not sure > on the consequences.. We have changed the Service URL that is passed to the > CAS-SERVER to the request URL and also the validation Service URL to the > same.... What issues does that bring up? > > Chris Whittle > SWAT Team Developer > J.B. Hunt Transport Services, Inc. > Office Phone:(479) 419-3122 > Ext:73122 > Fax Phone:(479) 820-1769 > chris_whit...@jbhunt.com > *What's your **next** move?**TM* > Intermodal | Dedicated | Truckload | LTL | Delivery | Refrigerated | > Flatbed | Expedited > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > scott.battag...@gmail.com > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
