Marvin, do you mean the host.name in the cas.properties file? It looked like the documentation wanted you to create a whole new properties file and such (even for cas 3.3.5). Isn't it as easy as editing the default value of the host.name property already defined? Also, am I correct in assuming that that value really could be any unique string and that it doesn't actually have to be a server name?
Curtis On Tue, May 4, 2010 at 8:36 AM, Marvin Addison <[email protected]>wrote: > > Has anyone used CAS in multiple server environments? > > I think lots of folks are doing HA CAS. We are. > > > What keeps the tokens unique? > > The server.name parameter in the cas.properties file. That string is > appended to the end of the service ticket by default to further > guarantee globally unique ticket strings. > > > is there any good articles on mutiple CA servers using the same token > (high availability). > > http://www.ja-sig.org/wiki/display/CASUM/Clustering+CAS is a good > starting point. I think searching the cas-user and cas-dev list > archives for "HA" and "Cluster" would provide further details after > you have a general understanding of the concerns involved in a HA CAS > setup. > > M > > -- > 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 > -- Curtis Garman -- 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
