Hi All,

Just tried it, the value of $host.name in uniqueIdGenerators.xml is from
cas/WEB-INF/cas.properties. That means we need to config cas.properties (or
other place holder properties file) for Clustering solution for guaranteeing
ticket uniqueness (even for CAS3.2.x).

Default config file: cas/WEB-INF/cas.properties

You can config it using out of box properties file using:

<bean id="placeholderConfig"
      
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
      <property name="locations">
            <list>
                  <value>file:/apps/local/share/etc/cas.properties</value>
             </list>
      </property>
</bean>



Thanks,
Qingfeng Zhang

2009/8/11 qingfeng zhang <[email protected]>

> Does that mean we still need to do configuration for that?
>
> Where the value of $host.name in uniqueIdGenerators.xml from?
>
> I deployed that solution using CAS3.2.1.1 (without configuration change in
> uniqueIdGenerators.xml) to two servers and both server generated ST/TGT with
> suffix 'cas' instead of server name.
>
> Thanks,
> Qingfeng Zhang
>
> 2009/8/10 Scott Battaglia <[email protected]>
>
>> We actually don't use the real host name (the variable just happens to be
>> called host.name).  Locally we call them "cas1" and "cas2" I believe
>> which has absolutely zero correlation to the actual machine names.
>>
>>
>>
>> On Mon, Aug 10, 2009 at 8:56 AM, Andrew Feller <[email protected]> wrote:
>>
>>> Michael,
>>>
>>> That definitely seems possible, however I think the reason hostname is
>>> used
>>> because it is difficult / impossible in a troubleshooting scenario to
>>> determine where tickets come from in a cluster if there isn't something
>>> meaningful.  It is true something else can be used, however it would be
>>> best
>>> if it was something known to ease those efforts.
>>>
>>> With that being said, I'm not saying your thought doesn't have merit.  I
>>> imagine if something was created and issued in a JIRA ticket that it
>>> would
>>> be included.
>>>
>>> Thanks,
>>> A-
>>>
>>>
>>> On 8/10/09 7:42 AM, "Michael Ströder" <[email protected]> wrote:
>>>
>>> > Andrew Feller wrote:
>>> >> 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.
>>> >
>>> > Hmm, in some environments it might not be acceptable for security
>>> reasons that
>>> > the real hostname of the CAS server is revealed to the browser. How
>>> about
>>> > generating a UUID (random-based, not the MAC address variant!) on every
>>> > startup and append that to the ticket?
>>> >
>>> > Ciao, Michael.
>>>
>>> --
>>> 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
>>>
>>>
>> --
>> 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

Reply via email to