for example the REST API that I wrap around couch has a call e.g. POST /myserver/create
If I make a signed request to this call how can I then use the OAuth handler in couch to validate the request? Surely you can only use the OAuth handler on signed requests sent to couch specific REST calls (e.g. http://127.0.0.1:5984/_session) mike On 28 February 2013 14:06, Alexander Shorin <[email protected]> wrote: > Hi, > > Just interesting, why built-in OAuth doesn't fits you? > -- > ,,,^..^,,, > > > On Thu, Feb 28, 2013 at 5:59 PM, Mike Harding <[email protected]> > wrote: > > Hi All, > > > > Having played around with the internal capabilities of couchdb's OAuth > > support it seems that I will need to implement a OAuth Proxy for my > > platform. > > > > I have a requirement to build a REST API that wraps around Couch. I want > > 3rd party apps to authenticate and send OAuth signed requests to my REST > > calls that will then make further calls to the couch REST API. > > > > I want to still use the _users db to manage entities in my system but I > > cant really use the internal OAuth to validate signed requests sent to my > > REST API. > > > > I'm just wondering what approaches people have used to do this, if this > > requires a OAuth proxy in front of couch what do people recommend? > > > > Cheers > > > > Mike >
