It seems reasonable to have the spec say that Token Endpoint errors can also be
returned from the Device Endpoint.
-- Mike
-----Original Message-----
From: OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of Justin Richer
Sent: Wednesday, April 12, 2017 12:19 PM
To: <oauth@ietf.org> <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Error Responses in Device Code Spec
Raising this point again. We’ve got a use case where people are wanting to do
custom error codes from the device endpoint and would like the spec to have
clear guidance. At the moment, it doesn’t even have examples for errors from
the device endpoint.
— Justin
> On Mar 15, 2017, at 12:33 PM, Justin Richer <jric...@mit.edu> wrote:
>
> Unless I’m missing something, the current device code spec doesn’t specify
> errors from the device code endpoint, only from the token endpoint. What are
> people implementing in practice? We’re using token endpoint style errors
> (invalid_client, inavlid_grant_type, etc).
>
> — Justin
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
