Error Message for Authentication Failure
Our configuration is tomcat without apache httpd server and CAS authentication.
When a user tries to access the Web CMS who does have a campus ID but does not have an account on the Web CMS, they get a reasonably messy error, akin to what follows. Anyway we can clean this up and generate a custom 500 failed login screen? Or even direct them back to the CAS login? What are our options (if any)?
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that
prevented it from fulfilling this request.
exception
javax.servlet.ServletException: External authentication failed:
Login failed
com.hannonhill.cascade.servlet.CustomAuthenticationServlet.doGet(CustomAuthenticationServlet.java:60)
javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
com.hannonhill.cascade.view.struts.request.SiteFilter.doFilter(SiteFilter.java:67)
org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:236)
org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167)
com.hannonhill.cascade.view.struts.security.AuthProtectFilter.doFilter(AuthProtectFilter.java:127)
org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:236)
org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167)
com.hannonhill.cascade.view.struts.request.ThreadLocalCacheFilter.doFilter(ThreadLocalCacheFilter.java:47)
com.hannonhill.cascade.view.struts.request.SetCharacterEncodingFilter.doFilter(SetCharacterEn
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by Tim on 10 Aug, 2012 08:20 PM
Hi David,
Unfortunately there aren't any good options at this time. I did find that we are aware of this issue and had created an item to address it here. In the description of that item, you'll see that we have a couple of potential solutions that we'll be exploring (with one of them being as you said - to allow for a custom 500 error page). Please continue to monitor that issue and we'll look to get it implemented in a future release of Cascade Server.
Let me know if you have any further questions.
Thanks
Tim closed this discussion on 04 Apr, 2013 04:18 PM.