To your questions: - The randomness of the generated token should suffice. The suffix in practice is mostly intended to identify the node issuing the ticket, which in clustered environment helps when you are trying to troubleshoot ticket replication. - Yes, although for reasons stated above, it's better if you choose a suffix the semi-identifies the node itself in order to see where tickets come from. There are extensions as well that help you determine the suffix automatically, if you intend to keep on cas.properties file across the cluster to help minimize change maintenance.
Please use the @cas-user mailing list for general Q&A on CAS. Regards, > -----Original Message----- > From: David Bala??ic [mailto:xerc...@gmail.com] > Sent: Thursday, May 08, 2014 7:15 AM > To: cas-dev@lists.jasig.org > Subject: [cas-dev] Ticket uniqueness clarification > > Hi! > > https://wiki.jasig.org/display/CASUM/Clustering+CAS says: > > Clustering > > Guaranteeing Ticket Uniqueness > > *If you are using CAS 3.2.x, feel free to skip this step. It is already > part > of your implementation. > > Since all the tickets need to be unique across JVMs, we will configure > this > part first, and it is the easiest part to do, too. > > (it goes on about setting up the host.name parameter) > -- > > I looked into the CAS 3.0.1 DefaultUniqueTicketIdGenerator source code and > it > does not support a suffix at all. > 3.1 already supports it and it is the same in newer versions. > > All versions (since at least 3.0.1) also use a random string in the ticket > string. > > So, can someone please clarify: > - when is ticket uniqueness a problem? (the random part should take care > of > it. Is it the small possibility that the random value could be the same?) > - using later versions, can the host.name parameter be the same left the > same across cluster nodes? (the web page mentioned above claims so if I > understand it correctly, even if my quick code inspection did not reveal > anything to support that) > > > Regards, > David Bala??ic > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > mmoay...@unicon.net 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
