Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 58160 invoked from network); 3 Nov 2010 09:25:59 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Nov 2010 09:25:59 -0000 Received: (qmail 41700 invoked by uid 500); 3 Nov 2010 09:26:29 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 41507 invoked by uid 500); 3 Nov 2010 09:26:26 -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 41497 invoked by uid 99); 3 Nov 2010 09:26:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Nov 2010 09:26:25 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ido.ran@gmail.com designates 209.85.214.180 as permitted sender) Received: from [209.85.214.180] (HELO mail-iw0-f180.google.com) (209.85.214.180) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Nov 2010 09:26:20 +0000 Received: by iwn37 with SMTP id 37so478655iwn.11 for ; Wed, 03 Nov 2010 02:26:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=ChFnoJT0f7t8qex2WObR78xPn5PN8DIf7rTxLHynLiE=; b=U2sKvkT3h6M4zKcxVpabsYB5JPUDxre6RwUW/K8mlStPMVVCRubc9N8C0VmJZkuMPK iALMDJ+MgyzRtFp8p/CUCBE50+9GsPoAKmKhj6Cm0MOpO9iRPpUove8sTbkTmLeV8VTQ RGV8AT3645cGLdn2864oyXtsNly74SvrJO9sM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=qLUoRxbQtaCV0s7xJ7OX907ddD0qFpQGEUdGWOv5OWVTHGkhay0qXLxFxpHYxNLf+p g1qALMWbE/WmrKApz+Il1DR51Nklijz7wTGmuQ82Bd5vbs6DbfhrAMFXvIPMCmpKPo0q FDH8pwdpwhQO8G3ub55YD8HHmTQ0DfdCk80BM= Received: by 10.231.35.131 with SMTP id p3mr15651637ibd.177.1288776360040; Wed, 03 Nov 2010 02:26:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.144.207 with HTTP; Wed, 3 Nov 2010 02:25:39 -0700 (PDT) In-Reply-To: References: From: Ido Ran Date: Wed, 3 Nov 2010 11:25:39 +0200 Message-ID: Subject: Re: OAuth example To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=00032557a2ba229ae5049422a149 --00032557a2ba229ae5049422a149 Content-Type: text/plain; charset=UTF-8 Hi, I hope it the right place to ask it. I want to write an application and I don't want my users to remember yet another username and password set. Does OAuth is the answer for it? Can I use it for single-sign-on using Gmail, Facebook, Yahoo or any other provider? Ido On Wed, Nov 3, 2010 at 10:44 AM, Doug wrote: > Basically, no. > > Even if it did implement the full set of actions, you'd still only be able > to use a couchdb login to login to other services, not vice versa... > > ~ > Doug. > > On Wed, Nov 3, 2010 at 3:52 PM, Wordit Ltd > wrote: > > > On Tue, Nov 2, 2010 at 10:18 AM, Martin Higham > > wrote: > > > > > > The CouchDB OAuth implementation is a partial implementation that > > supports > > > the OAuth signing of requests where the client has it's client > > credentials > > > and knows the user's access token. > > > > Does that mean you can let users log in via their OpenID, Twitter or > > Facebook account? That's what I couldn't figure out yet. > > > > If not, is it at all possible with CouchDB? Many commenting systems > > use that now and it's great not to require additional signups. > > > > Marcus > > > --00032557a2ba229ae5049422a149--