Hi
in ticketExpirationPolicies.xml file you have bean with
id="grantingTicketExpirationPolicy".
Write your own policy and put here your class name.
We have overrided default expire method.
Our own asks all services wheather user is still active.
Michal Pysz
Hi,
This is mainly a question to CAS developers.
CAS-686 was fixed in 3.3.5. I would like to understand the motivation behind it
and maybe override the behavior.
1. Why should a user be logged out of an application just because the CAS
ticket expired, which is actually just because he/she did not login to another
application? in the JIRA issue itself
(https://issues.jasig.org/browse/CAS-686?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel#issue-tabs)
it is mentioned that this behavior may not be appropriate to all systems, yet
it was decided to implement it without an apparent way to override it. Why?
2. How can I override this behavior? I do not see it is configurable in any
way. I can maybe extend TicketGrantingTicketImpl and implement expire() such
that it does not invoke logOutOfServices(), but I do not see where I can
configure CAS to use my implementation.
Thanks in Advance,
Moshe
--
Michał Pysz
Sekcja Systemów Informacyjnych
Dział Technologii Informacyjne
Uniwersytet Jagieloński w Krakowie
Information Systems Section
Information Systems Department
Jagiellonian University at Krakow, Poland
--
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
