RESTful API: status when authentication fails?

Scott Battaglia scott.battaglia at gmail.com
Mon Sep 22 21:46:09 EDT 2008


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 <lastobelus at mac.com>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
> lastobelus at mac.com
>
>
>
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20080922/ddc44abf/attachment.html 


More information about the cas mailing list