in prior version 4.0.x we were .. slo.tgtExpiredCallbacks.enabled to
false.. can can we achieve this behavior with 4.2.7?
Ticket Registry Cleaner Behavior
Furthermore, the default behavior is to issue single sign out callbacks in
response to a logout request or when a TGT is expired via expiration policy
when a TicketRegistryCleaner runs. If you are using ticket registry cleaner
and you want to enable the single sign out callback only when CAS receives
a logout request, you can configure your TicketRegistryCleaner as such:
<bean id="ticketRegistryCleaner"
class="org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner"
p:ticketRegistry-ref="ticketRegistry"
p:lock-ref="cleanerLock"
p:logUserOutOfServices="${slo.callbacks.disabled:false}" />
On Wednesday, October 4, 2017 at 4:02:16 PM UTC-7, satnam wrote:
>
> Hello,
>
> we are using 4.2.7 and noticed that when CAS send SLO request to
> applications when user does not use TGT within 2 hours. Is there a way to
> disable sending SLO when ticket registry cleaner removed the TGT? we want
> to applications to receive SLO requests when user click on signout on any
> of application but not when user stay on one site for more than 2 hours.
>
> thank for your help
>
>
>
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/6abed4d8-d9c9-43ac-afed-57471063e22d%40apereo.org.
