[ https://issues.apache.org/jira/browse/GUACAMOLE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Couchman updated GUACAMOLE-355: ------------------------------------ Attachment: guac-cas-invalid-login.png guac-cas-insufficient-login.png > 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 > Attachments: castrace.txt, guac-cas-insufficient-login.png, > guac-cas-invalid-login.png > > > 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)