Re: [OAUTH-WG] error codes in 4.1.2.1 and 4.2.2.1 and extension response types (8.4)

2012-02-07 Thread Roger Crew
r.t. 'unsupported_grant_type' > > Changed the definition of invalid_request to: > > The request is missing a required parameter, includes an invalid > parameter value, or is otherwise malformed. Just noticed in draft 23 that you changed 4.2.2.1 but didn't change 5.

Re: [OAUTH-WG] error codes in 4.1.2.1 and 4.2.2.1 and extension response types (8.4)

2011-12-05 Thread Roger Crew
ies if this was obvious and someone already took care of it for the next draft, but the lack of response led me to believe this issue was falling through the cracks. And it seems likely I hit a really busy spot in last month's schedule. Thanks for your time...) Roger Crew a.k.a. someone

[OAUTH-WG] non-TLS clients and making the state parameter be use-once for authcode requests

2011-11-16 Thread Roger Crew
to the browser, is COMPLETELY USELESS in OAuth2, At which point I don't understand why the current spec doesn't just require TLS clients and call it a day. -- Roger Crew 206.940.5732 c...@cs.stanford.edu ___ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth

[OAUTH-WG] error codes in 4.1.2.1 and 4.2.2.1 and extension response types (8.4)

2011-11-13 Thread Roger Crew
;, i.e., to allow the server to respond EITHER as per 4.1.2 or 4.2.2 as it sees fit (but evidently WG members are not agreeing on whether this response_type is needed, hence its absence from the current spec other than as a remark in 8.4). -- Roger Crew c...@cs.stanford.edu ___ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth