That's up to how your Flex application is configured since that is what
would be requesting tickets to send to the backend service.

Cheers,
Scott


On Mon, Apr 27, 2009 at 3:09 AM, Spruit, Richard
<[email protected]>wrote:

>  Thanks! But is does not explain why sometimes every call gets a (new)
> ticket, and sometimes only the first call gets a ticket.
>
>
>
> Any light on that subject?
>
>
>
> Thanks in advance!
>
>
>
> Richard
>
>
>
> *From:* Scott Battaglia [mailto:[email protected]]
> *Sent:* maandag 27 april 2009 3:40
> *To:* [email protected]
> *Subject:* Re: [cas-user] A lot of tickets
>
>
>
> Its up to how you set up your application and backend service.  If you use
> Spring Security to secure your backend you can control how long the same
> service or proxy ticket is valid for.
>
> Cheers,
> Scott
>
>  On Sun, Apr 26, 2009 at 9:00 AM, Spruit, Richard <
> [email protected]> wrote:
>
> We have build an Flex application which is autorisated by CAS. This Flex
> application sends requests to a back end service which is also autorisated
> by CAS. Sometimes we see in the log of this backend-service a ticket on the
> first request to the backend service, and no tickets on subsequent requests.
> However, sometimes we see in the log a (new) ticket on every request to this
> backend service (usually 20 subsequent requests). Having a new ticket on
> every request is not ideal in terms of performance.
>
> Is there a way we can influence this bahaviour? Preferably, we would like
> to see a ticket on the first request, not on subsequent requests from the
> same backend-service.
>
> Thanks in advance,
>
> Richard
>
>
>
>
>
> Please help Logica to respect the environment by not printing this email  /
> Pour contribuer comme Logica au respect de l'environnement, merci de ne pas
> imprimer ce mail /  Bitte drucken Sie diese Nachricht nicht aus und helfen
> Sie so Logica dabei die Umwelt zu schuetzen  /  Por favor ajude a Logica a
> respeitar o ambiente nao imprimindo este correio electronico.
>
>
>
> This e-mail and any attachment is for authorised use by the intended
> recipient(s) only. It may contain proprietary material, confidential
> information and/or be subject to legal privilege. It should not be copied,
> disclosed to, retained or used by, any other party. If you are not an
> intended recipient then please promptly delete this e-mail and any
> attachment and all copies and inform the sender. Thank you.
>
>
> --
> 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
>
>
> Please help Logica to respect the environment by not printing this email /
> Pour contribuer comme Logica au respect de l'environnement, merci de ne pas
> imprimer ce mail / Bitte drucken Sie diese Nachricht nicht aus und helfen
> Sie so Logica dabei die Umwelt zu schuetzen / Por favor ajude a Logica a
> respeitar o ambiente não imprimindo este correio electrónico. This e-mail
> and any attachment is for authorised use by the intended recipient(s) only.
> It may contain proprietary material, confidential information and/or be
> subject to legal privilege. It should not be copied, disclosed to, retained
> or used by, any other party. If you are not an intended recipient then
> please promptly delete this e-mail and any attachment and all copies and
> inform the sender. Thank you.
>
> --
> 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