Forum OpenACS Development: Re: Strict RFC 3986 url encoding


	The Toolkit for Online Communities 15900 Community Members, 0 members online, 2226 visitors today			Log In	Register

Forum OpenACS Development: Re: Strict RFC 3986 url encoding

OpenACS Home : Forums : OpenACS Development : Re: Strict RFC 3986 url encoding : One Message

Back to OpenACS Development

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?

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.

Back to OpenACS Development