From user-return-18231-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Sat Oct 8 03:05:33 2011 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 C152172A8 for ; Sat, 8 Oct 2011 03:05:33 +0000 (UTC) Received: (qmail 5735 invoked by uid 500); 8 Oct 2011 03:05:31 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 5705 invoked by uid 500); 8 Oct 2011 03:05:31 -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 5691 invoked by uid 99); 8 Oct 2011 03:05:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Oct 2011 03:05:30 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of maxosmail@gmail.com designates 209.85.215.180 as permitted sender) Received: from [209.85.215.180] (HELO mail-ey0-f180.google.com) (209.85.215.180) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Oct 2011 03:05:26 +0000 Received: by eya25 with SMTP id 25so1834582eya.11 for ; Fri, 07 Oct 2011 20:05:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=vOg4OjFjCdkU3puZInA4QZUtAA1IJE+gEsWhn1XJ4dA=; b=D//e5wJwQ+AAcJ0i4pcMvp2kqWXNlGBh9fFPPxX3VZ482aY/h1Q1W+2ChBSyuNnjuS TcP7pMWrNzRhLPmDMSgYyT19qodzUFjcqkfCol0SKP0YfigRvak4Ocxx/ADgddsc72hW BbnK7IwRCoXX/wPK3WLlcLTQxnMklAVjgGQto= Received: by 10.14.4.229 with SMTP id 77mr847992eej.9.1318043104337; Fri, 07 Oct 2011 20:05:04 -0700 (PDT) MIME-Version: 1.0 Sender: maxosmail@gmail.com Received: by 10.14.28.202 with HTTP; Fri, 7 Oct 2011 20:04:44 -0700 (PDT) In-Reply-To: References: From: Max Ogden Date: Fri, 7 Oct 2011 20:04:44 -0700 X-Google-Sender-Auth: 7uYM8LE-3p_O48-eHN7pKLpwS8o Message-ID: Subject: Re: Working example for OAuth with Facebook and/or Google? To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=0016363ba3260862d004aec0d33f --0016363ba3260862d004aec0d33f Content-Type: text/plain; charset=UTF-8 Hi Stephan, The OAuth in couch is meant to provide OAuth verification as opposed to what you want which is a relying party OAuth login client. Long story short Couch can't log in to Twitter or Facebook on it's own. 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 Cheers, Max On Fri, Oct 7, 2011 at 7:42 AM, Stephan Wissel wrote: > Hi there, > > still new with CouchDB, so pardon my n00b question. > > 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=%28Oauth%29 > >and > thelocal.ini > < > http://wiki.apache.org/couchdb/Configurationfile_couch.ini?highlight=%28Oauth%29 > >configuration > and HTTP command< > http://wiki.apache.org/couchdb/Complete_HTTP_API_Reference?highlight=%28Oauth%29 > >documentation. > What I understand is: > > - 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) > > What I don't understand: > > - 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 > > So what U'm looking for is a sample application to learn from. Where could > I > find one? > > Phone: +65 96673269 > Blog Twitter > Google+ > Facebook > LinkedIn > Xing > Sametime *Skype* > --0016363ba3260862d004aec0d33f--