Nick Couchman commented on GUACAMOLE-355:

Sorry, no insult meant there...just continuing a series of bad puns...

Anyway, I was able to catch the exception and throw a 
GuacamoleInvalidCredentialsException, which results in a redirect to the 
Guacamole login page and a prompt for username/password.  At the moment I 
cannot get this to actually display the error message, though - not sure why it 
just gives the blank login page and no error.  Anyway, if I can get the error 
message to show up I think this will take care of this issue.

> 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
> 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

Reply via email to