Currently TicketResource returns http status CLIENT_ERROR_BAD_REQUEST  
regardless of why the ticket creation request failed. Should it not  
return status  CLIENT_ERROR_FORBIDDEN if authentication failed due to  
bad credentials? The exception is chained so to patch this I guess I  
have to figure out how to handle chained exceptions.



Cheerio,

Michael Johnston
[EMAIL PROTECTED]




_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to