Elucian Banner 5 minute timeout with CAS

[Adam Causey]

We are experiencing a 5 minute session timeout after users login to our Elucian Banner system via CAS. We think it's an issue in Banner, but wanted to see if anyone else has come across the issue.  

It only seems to occur when the user already has an existing CAS SSO session (TGT cookie), and not if they are starting a new login from CAS when going into Banner.

Here is how we are able to replicate the issue:

1) User logs into a CAS-enabled application (other than Banner)

2) User goes into Banner via its SSO URL (this will redirect to CAS, which sends a 302 back with a ticket)

3) After no activity in Banner for 5 minutes the user returns and refreshes the page. A popup that says "Session Timeout Occurred" is displayed to the user.

We have SLO disabled in our CAS instance (due to previous issues with it automatically logging out Blackboard users).

Thanks for any help you can provide.

-Adam

[Ray Bon]

Adam,

Is the TGC still active, that is can you access a third CAS SSO enabled application?
Check CAS logs to see if Banner is sending a logout request to CAS.
If the TGC is still alive, then it must be a Banner config.

I am not far enough along in CAS setup to poke at Banner and provide more detail.

Ray

--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
---
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 cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/CAN6MV5Op8%2BZmgB3vAq%2BaNHbjRwwGA_w7Y4jozVb605SGXFXcag%40mail.gmail.com.

-- 
Ray Bon
Programmer Analyst
Development Services, University Systems
2507218831 | CLE C023 | rb...@uvic.ca

[Christopher Myers]

Try this change, and then repackage and redeploy the CAS war:

modify the value of CAS's web.xml file, change the default timeout to 2 hours

  <session-config>
    <!-- Default to 5 minute session timeouts -->
    <session-timeout>120</session-timeout>
  </session-config>

>>> Adam Causey <apca...@vcu.edu> 02/15/17 10:45 AM >>>