If we don't we may be able to return the message from the exception (if there is one). If you want, you can open a JIRA issue to track this.
Thanks -Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Mon, Sep 22, 2008 at 10:03 PM, Michael Johnston <[EMAIL PROTECTED]>wrote: > I suppose. It's nice to know the difference between a broken mechanism and > incorrect credentials though. > Here is my change as a patch: > > > > > Cheerio, > > Michael Johnston > [EMAIL PROTECTED] > > > > > On 22-Sep-08, at 6:46 PM, Scott Battaglia wrote: > > There's nothing really to forbid. You didn't log in using one of the > standard HTTP Authentication mechanisms. You're trying to obtain a TGT and > gave bad input. > > -Scott > > -Scott Battaglia > PGP Public Key Id: 0x383733AA > LinkedIn: http://www.linkedin.com/in/scottbattaglia > > > On Mon, Sep 22, 2008 at 9:31 PM, Michael Johnston <[EMAIL PROTECTED]>wrote: > >> 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 >> > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > > > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
