[
https://issues.apache.org/jira/browse/GUACAMOLE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099401#comment-16099401
]
Nick Couchman commented on GUACAMOLE-355:
-----------------------------------------
So, turns out this is a little more complex than just missing error handling in
the CAS module. What's happening in this case is that the CAS module is
triggering a redirect to the ticket validation service, which is picked up by
the RESTExceptionWrapper. When the URL is incorrect for the CAS module, it
throws a FileNotFoundException, which is intercepted by the
RESTExceptionWrapper, which generates a internal server error (500) and never
returns control to the CAS module.
Not entirely sure how to proceed on this one, but I'll give a few things a
shot...any help would be appreciated...
> CAS Module Missing Error Handling
> ---------------------------------
>
> Key: GUACAMOLE-355
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-355
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-auth-cas
> Affects Versions: 0.9.13-incubating
> Reporter: Nick Couchman
> Assignee: Nick Couchman
>
> As reported by Kaushnik on the dev mailing list, attempting to use the
> guacamole-auth-cas module with an incorrect CAS authentication endpoint
> results in very generic and not very useful 500 Internal Server errors rather
> than meaningful messages that point the user in the right direction for
> correcting the error. Need to see if the CAS framework has any built-in
> error checking facilities and try to leverage those, or at least throw some
> more meaningful Guacamole errors when we run into problems.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
