Re: [OAUTH-WG] OAuth 2.0 Bearer Token Specification draft -06

2011-07-25 Thread Mike Jones
[mailto:i...@mckellar.org] Sent: Sunday, July 10, 2011 1:16 PM To: Mike Jones Cc: oauth@ietf.org Subject: Re: [OAUTH-WG] OAuth 2.0 Bearer Token Specification draft -06 Hi, I'm reading through draft 6 of the bearer token spec and had a question about one of the examples. In section 2.4 there's

Re: [OAUTH-WG] OAuth 2.0 Bearer Token Specification draft -06

2011-07-10 Thread Ian McKellar
Hi, I'm reading through draft 6 of the bearer token spec and had a question about one of the examples. In section 2.4 there's an error response example when an expired token is used: HTTP/1.1 401 Unauthorized WWW-Authenticate: Bearer realm=example error=invalid_token,

Re: [OAUTH-WG] OAuth 2.0 Bearer Token Specification draft -06

2011-06-29 Thread Bill
This is a much clearer draft, thanks. I'm looking at support for this at the moment and are wondering is there much implementer experience to date with bearer tokens, and/or how stable the wg think the draft is at this point? Bill On 23/06/11 01:53, Mike Jones wrote: I’ve published draft 06

[OAUTH-WG] OAuth 2.0 Bearer Token Specification draft -06

2011-06-22 Thread Mike Jones
I've published draft 06http://self-issued.info/docs/draft-ietf-oauth-v2-bearer-06.html of the OAuth Bearer Token Specificationhttp://self-issued.info/docs/draft-ietf-oauth-v2-bearer.html. It contains the following changes: * Changed parameter name bearer_token to access_token, per