Which CAS 5.x release are people running successfully in prod?

[Duane Booher]

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

[joj...@gmail.com]

We are running 5.1.5 successfully. But that is relative since we are using specific features that you may not be using.

Sent from a device.

--
- 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 cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/fb05fa6d-fe02-4b85-98ce-cef694947ed0%40apereo.org.

[Ray Bon]

Duane,

Can you itemize what is not working in your production environment?

Ray

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

[Duane Booher]

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 

[Man H]

Hi Duanne,

your comments make me consider whereas to move on to 5.0.x. last RELEASE version (now on 5.0.10) or not.

I myself found other problems, luckily on testing phase, one of them error when starting 5.0.10 with oauth support. It only worked with 5.0.4.

Another (minor) issues is that of tomcat not shutting down well with standard shutdown scripts, and logging in two different directories (one empty entry in root) and the others on specified  <Property name="cas.log.dir" >logs</Property>.

These compared to yours are quite harmless.

Maybe there is a missing way of reporting problems which we dont know.

Me myself mentioned these on  mailing list with no answer at all :).

Man H

--

- 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 cas-user+unsubscribe@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/05306c6c-5bff-46f2-af51-76100c50aab7%40apereo.org.

[Uxío]

With no offense intention Sir,

(first of all) I can not seriously be suspect of any CAS nor the CAS team (not even the big pile of sh Java is) fandom,

and I do not have exposure to CAS version 5 (specifically), still

(and but) I find a hard time in getting to believe one whole minor CAS version can be affected of a bug such that such a core-y feature of CAS as SSO session persistence would get effectively capped at half an hour.

Letting us hope I am wrong, I suspect it is somewhat likely any you did or got something wrong.

Wishing you best of luck, regards,

Sent from my iPhone

--

- 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 cas-user+u...@apereo.org.

[Man H]

Thank you Sir 

your words touched me deep inside and made me promise not to sent any more issues regarding problems that, you made me see it, thanks lord, are only my mistakes , because you don't make them, and you don't even bother to take into consideration nor answer them because you are busy answering support requests .

So again, thank you for your valuable time in writing those very useful words, 

Wishing you the best and warmest regards,

To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscribe@apereo.org.

To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/05306c6c-5bff-46f2-af51-76100c50aab7%40apereo.org.

--

- 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 cas-user+unsubscribe@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/BE1EA11A-C6E0-41BB-90D3-F6B2295A9497%40madiva.com.

[Paul]

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.