Fortunately, Miami University is in a position to facilitate addressing
this issue. Thanks to the efforts of Unicon (https://www.unicon.net/) the
latest snapshot build of 5.3.7 appears to address this issue. If anyone
else is following this and can help test the Google Apps integration,
please do
I just reproduced the broken behavior using CAS 5.3.5 and 5.3.7-SNAPSHOT.
We are preparing to upgrade our CAS server but have not tested Google Apps
since our initial work with 5.2.x, when it did work correctly IIRC.
We are going to pursue pretty aggressively because it has major
consequences for
I patched the CompressionUtils file and replaced the inflate function with
the one from 5.1.x and now GoogleApps is working again.
Was there a reason the function was re-written in the first place other
than trying to make it more efficient? I'm thinking of submitting a pull
request to revert
After a lot of debugging, I have discovered that the XML is not being
properly inflated in AbstractSaml20ObjectBuilder at line 442:
CompressionUtils.inflate(decodedBytes);
java is complaining about the zip header
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom:
I've traced the problem to the SamlServiceFactory class. It seems as though
service and requestBody are always null. Trying to debug the issue.
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions:
