Qingfeng, In CAS 3.2.X, there was a change in the Spring configuration such that the hostname of the server is being included automatically within the Spring beans used to generate tickets. If you look in the /WEB-INF/spring-configuration/uniqueIdGenerators.xml ( https://www.ja-sig.org/svn/cas3/tags/cas-3-2-0-final/cas-server-webapp/src/m ain/webapp/WEB-INF/spring-configuration/uniqueIdGenerators.xml ), you will see several Spring property placeholders of ${host.name}. This will make your TGTs and STs end with the machine¹s name thus allowing them to be different within a cluster.
HTH, A- On 8/10/09 1:25 AM, "qingfeng zhang" <[email protected]> wrote: > > In http://www.ja-sig.org/wiki/display/CASUM/Clustering+CAS, it has the > description: > Guaranteeing Ticket Uniqueness > *If you are using CAS 3.2.x, feel free to skip this step. It is already part > of your implementation. > > Is that mean no need to do any configuration for guaranteeing ticket > uniqueness in CAS 3.2.x? > > I have checked the code/configuration, it seems still need to change the > host-name per server. > > Thanks, > Qingfeng Zhang -- Andrew Feller, Business System Programmer LSU University Information Services 200 Frey Computing Services Center Baton Rouge, LA 70803 Office: 225.578.3737 Fax: 225.578.6400 -- 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
