Forum OpenACS Development: Re: Strict RFC 3986 url encoding

Collapse
5: Re: Strict RFC 3986 url encoding (response to 1)
Posted by Dave Bauer on 10/04/11 01:18 AM
Hi,

Can you share your OAuth Code?

Collapse
6: Re: Strict RFC 3986 url encoding (response to 5)
Posted by Steffen Tiedemann Christensen on 10/04/11 07:19 AM
Hey Dave,

Are you looking for a client implementation of OAuth 1.0a or for something broader?

(Actually Guan's project ended up in both a server and client side library, so there's something to share at least -- we've just never cleaned it up sufficiently to do so. This would serve as a good opportunity.)

Steffen

Collapse
7: Re: Strict RFC 3986 url encoding (response to 6)
Posted by Dave Bauer on 02/29/12 06:02 PM
Hi,

Any updates on this? Did you ever implement OAuth 2?

Has anyone else implemented OAuth 2 as now required by most services?

Collapse
8: Re: Strict RFC 3986 url encoding (response to 7)
Posted by Guan Yang on 02/29/12 06:04 PM
I haven't seen anything, but OAuth 2 should be much easier because there's no special signature generation required. You just open an HTTPS connection and pass the token.