> -Original Message-
> From: Marius Scurtescu [mailto:mscurte...@google.com]
> Sent: Wednesday, May 19, 2010 5:43 PM
> To: Eran Hammer-Lahav
> Cc: Yaron Goland; OAuth WG (oauth@ietf.org)
> Subject: Re: [OAUTH-WG] Open Issues: Group Survey (respond by 5/13)
>
> On Mon, May 17, 2010 at 11:
Marius,
> Only direct responses are JSON, form/url encoded
> still has to be used:
> - direct requests
> - through browser requests
> - through browser responses
> - through browser fragment responses
A better solution would be to change the last two (token info delivered in a
callback URIs) so
I think there are a few open issues around Native App support.
While all flows can be used by native apps I am referring only to the
ones that involve a browser:
- web server
- user-agent
- device
For the web server flow to support native apps we need to clarify:
- un-registered clients, I think
On Mon, May 17, 2010 at 11:26 PM, Eran Hammer-Lahav wrote:
> Now, this is useful.
Yes, it is very useful.
One minor correction, forms do support multi-value fields. Also, XML
supports name spaces.
> I think this raises a very good point. Unless we expect the server response
> to always be jus
Sweet!
http://groups.google.com/group/37signals-api/browse_thread/thread/86b0da52134c1b7e
> OAuth 2 is a standard way for third-party apps to get authorized access to
> a user's account without needing to copy/paste API keys or ask users for
> sensitive usernames and passwords.
> We've added O
The interim working meeting will be held tomorrow in Sunnyvale, CA, hosted
by Yahoo!:
701 1st Ave
Building E classroom 9
Sunnyvale, CA
We will start at 9am with a lunch bread at 12:30 and a snack break at 3pm.
Parking is available next to building E, but if you cannot find parking,
please use th
