Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DEEEF7860 for ; Sat, 8 Oct 2011 07:53:42 +0000 (UTC) Received: (qmail 21021 invoked by uid 500); 8 Oct 2011 07:53:41 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 20867 invoked by uid 500); 8 Oct 2011 07:53:38 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 20859 invoked by uid 99); 8 Oct 2011 07:53:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Oct 2011 07:53:37 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of martinh@gmail.com designates 74.125.82.54 as permitted sender) Received: from [74.125.82.54] (HELO mail-ww0-f54.google.com) (74.125.82.54) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Oct 2011 07:53:31 +0000 Received: by wwf5 with SMTP id 5so6200022wwf.23 for ; Sat, 08 Oct 2011 00:53:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:references:from:content-type:x-mailer:in-reply-to :message-id:date:to:content-transfer-encoding:mime-version; bh=2d1rgITS8iYnvNvZhcUs6d1pfDC4HJcFSeytzikPCU0=; b=PGt5dpiwyZyzVgc505wMF2f5Yr5Uz3xzD+7PvD/knTMTnxpt2/dVrb5mTLhWSoMAYW BHifDAhQBBFlewJsNGKy2XrvDwqJas86xjDkzHJ5nI83sH0LUw8tHqtBCNO97DsU7TAp o2EQ9QY8HEpzO2kU89Jvw9SY9pcaBFnOCxFWM= Received: by 10.227.28.131 with SMTP id m3mr3448571wbc.60.1318060390871; Sat, 08 Oct 2011 00:53:10 -0700 (PDT) Received: from [192.168.0.6] (host86-166-111-216.range86-166.btcentralplus.com. [86.166.111.216]) by mx.google.com with ESMTPS id a12sm12507246wbo.9.2011.10.08.00.53.09 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 08 Oct 2011 00:53:09 -0700 (PDT) Sender: Martin Higham Subject: Re: Working example for OAuth with Facebook and/or Google? References: From: Martin Higham Content-Type: text/plain; charset=us-ascii X-Mailer: iPad Mail (9A334) In-Reply-To: Message-Id: <5CA51C2C-5BFE-428B-8B08-121AE90017C9@ocasta.co.uk> Date: Sat, 8 Oct 2011 08:53:07 +0100 To: "user@couchdb.apache.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) X-Virus-Checked: Checked by ClamAV on apache.org There's also our Facebook Authentication module for Couch on GitHub https://github.com/ocastalabs/CouchDB-Facebook-Authentication On 8 Oct 2011, at 04:04, Max Ogden wrote: > Hi Stephan, >=20 > The OAuth in couch is meant to provide OAuth verification as opposed to wh= at > you want which is a relying party OAuth login client. Long story short Cou= ch > can't log in to Twitter or Facebook on it's own. >=20 > Here's a node.js authentication server that handles Twitter OAuth and then= > provisions couch users: > https://github.com/maxogden/datacouch/tree/master/processors/auth >=20 > Cheers, >=20 > Max >=20 > On Fri, Oct 7, 2011 at 7:42 AM, Stephan Wissel wrote:= >=20 >> Hi there, >>=20 >> still new with CouchDB, so pardon my n00b question. >>=20 >> I want to create a public CouchApp where users login using their Facebook= , >> Google or other OAuth accounts. I did read the security feature >> overview< >> http://wiki.apache.org/couchdb/Security_Features_Overview?highlight=3D%28= Oauth%29 >>> and >> thelocal.ini >> < >> http://wiki.apache.org/couchdb/Configurationfile_couch.ini?highlight=3D%2= 8Oauth%29 >>> configuration >> and HTTP command< >> http://wiki.apache.org/couchdb/Complete_HTTP_API_Reference?highlight=3D%2= 8Oauth%29 >>> documentation. >> What I understand is: >>=20 >> - In the INI file I can activate Oauth >> - Some magic I don't need to understand will then come back and say >> "Hey this is Joe Doe" >> - I need to take care of my own authorization (e.g. now I know he is Joe= , >> let's see what I allow him to do) >>=20 >> What I don't understand: >>=20 >> - How would one build a CouchApp where a user register him/herself using= >> OAuth >> - Where do the keys get stored, so my app is known to the OAuth provider= >>=20 >> So what U'm looking for is a sample application to learn from. Where coul= d >> I >> find one? >>=20 >> Phone: +65 96673269 >> Blog Twitter >> Google+ >> Facebook >> LinkedIn >> Xing >> Sametime *Skype* >>=20