On Fri, 12 Dec 2014, David A. Kovacic wrote:
What we are seeing in the 2 events we have been able to capture much
information on is that in both cases the individuals were making their
repeated SAML requests to either Hangouts or GTalk from a Windows (we
think 8) box running Chrome. It may be the newly released "hangouts"
extension for Chrome that is causing something, however even if it is a
bug in an extension or Chrome itself, it should not be able to fill the
heap memory of the SSO server which would argue that there is some bug
in the CAS SAML code that is being "excercised" by the repeated logins.
It sounds to me like the CAS SAML code isn't releasing the memory used by
the SAML response after it has been sent.
You could always run Shibboleth for the Google SAML integration instead...
:)
Andy
--
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
