Hi Duanne,
Have you had any success with this? I am in the same boat with respect to
any version of CAS > 5.0.5 breaks proxy tickets. Unfortunately 5.0.5 is
not production ready and requires constant restarts due to memory leaks.
We can also crash it fairly quickly doing load tests with service tickets
only with over 8 GB of heap.
I'm looking at reverting to a stable version of CAS like 4.2.X unless I can
solve the proxy ticket issue. 5.2.3 seems stable related to service
tickets; except proxy configuration is not working as documented.
So far what we found is this is always throws a null pointer; and sure
enough in the cas code it isn't initialized; which leads me to believe
there is some configuration missing that is supposed to do you a favor.
2018-03-21 13:34:06,537 ERROR
[org.apache.catalina.core.ContainerBase.[Tomcat].[localhost].[/cas].[dispatcherServlet]]
- <Servlet.service() for servlet [dispatcherServlet] in context with path
[/cas] threw exception [Request processing failed; nested exception is
java.lang.NullPointerException] with root cause>
java.lang.NullPointerException
at
org.apereo.cas.web.ProxyController.getTargetService(ProxyController.java:102)
~[cas-server-support-validation-5.0.10.jar!/:5.0.10]
at
org.apereo.cas.web.ProxyController.handleRequestInternal(ProxyController.java:78)
~[cas-server-support-validation-5.0.10.jar!/:5.0.10]
thanks in advance.
On Thursday, November 16, 2017 at 4:05:52 PM UTC-8, Duane Booher wrote:
>
> First off, we are running CAS 5.0.5 because that is the latest 5.0.x
> version that we get cas/poxy to work.
>
> The problems we've encountered - First, when zero days are left on the
> LDAP password expiration policy, then a CREDENTIAL_NOT_FOUND occurs
> instead of the PASSWORD_EXPIRED. Another error is that we encountered a
> heap out of memory error and we are running at 6G heap. Another error is
> that SSO session persistence across multiple app tabs on same browser was
> not lasting longer than 30 minutes.
>
> There are additional circumstances for all the above, but bottom line is
> that all of these issues work as expected on CAS 4.0.3.
>
> We are starting to configure a CAS 5.2 system to evaluate the above
> functionality.
>
> Duane
>
> On Thursday, November 16, 2017 at 3:50:03 PM UTC-7, rbon wrote:
>>
>> Duane,
>>
>> Can you itemize what is not working in your production environment?
>>
>> Ray
>>
>> On Thu, 2017-11-16 at 08:21 -0800, Duane Booher wrote:
>>
>> Hi, we have been trying to upgrade to CAS 5.x in our production
>> environment. We run successfully in our CAS-Test, but in our prod
>> environment we encounter various issues forcing us to revert back to CAS 4.
>>
>> What CAS 5.x releases are people successfully running in production?
>>
>> Duane Booher
>>
>> --
>> Ray Bon
>> Programmer analyst
>> Development Services, University Systems
>> 2507218831 | CLE 019 | [email protected]
>>
>>
--
- 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/f2ba523a-a1f9-482c-9304-84ae1148cc5d%40apereo.org.
