IETF Logo Mail Archive

Re: [OAUTH-WG] Text for Native Applications

Brian Eaton <beaton@google.com> Wed, 01 June 2011 16:48 UTC

Return-Path: <beaton@google.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8357E06FB for <oauth@ietfa.amsl.com>; Wed, 1 Jun 2011 09:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.177
X-Spam-Level:
X-Spam-Status: No, score=-106.177 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oy+mbjnH2IAg for <oauth@ietfa.amsl.com>; Wed, 1 Jun 2011 09:48:40 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id DD027E06DC for <oauth@ietf.org>; Wed, 1 Jun 2011 09:48:39 -0700 (PDT)
Received: from kpbe15.cbf.corp.google.com (kpbe15.cbf.corp.google.com [172.25.105.79]) by smtp-out.google.com with ESMTP id p51GmcqP009290 for <oauth@ietf.org>; Wed, 1 Jun 2011 09:48:38 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1306946918; bh=xYZyY97Tmwbbbv4Gyxi26amwCqA=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=r+PWJeZqJjQfWQ1VeJdGEcnltQktJdCMOHIrluieq2erQG36ubayY7jMV6emfXKJg YmkeibSgp7cKEMT/St58g==
Received: from pzk26 (pzk26.prod.google.com [10.243.19.154]) by kpbe15.cbf.corp.google.com with ESMTP id p51GmaTo002666 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <oauth@ietf.org>; Wed, 1 Jun 2011 09:48:36 -0700
Received: by pzk26 with SMTP id 26so3167388pzk.24 for <oauth@ietf.org>; Wed, 01 Jun 2011 09:48:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=cs5enPekR9vBfu6j+59sMouJRmz1it4QRmXjzS0D22Q=; b=pX94IRnN73iq7BBVJ7I7AU91A+cSQrovvjJQOesa/T9d8r5ADls2TKENJCLWxuYFDs ny/+yI/c1J1edFiRN9zQ==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=BR06BrB3fxw8K4Z/34sHq8c4eyKG0sG4KDaNO81Y7cP/w4Uj4ZsahNoSdydXaTciKy Vj1ylSIsrmuQH1OpJ7dQ==
MIME-Version: 1.0
Received: by 10.142.202.2 with SMTP id z2mr1304822wff.266.1306946916088; Wed, 01 Jun 2011 09:48:36 -0700 (PDT)
Received: by 10.142.14.2 with HTTP; Wed, 1 Jun 2011 09:48:35 -0700 (PDT)
In-Reply-To: <755100.21182.qm@web31816.mail.mud.yahoo.com>
References: <BANLkTi=Gd1oFWpQHRs6tZ_LUxu+VOmKPAYbKFUENdfCvNcu5CQ@mail.gmail.com> <CA0B2D34.1AA93%cmortimore@salesforce.com> <BANLkTimZpSdNsSx0xjc7JtVMNMRCow0Y+Q@mail.gmail.com> <4DE5EE7F.4040907@lodderstedt.net> <BANLkTi=z1M6CKHQdnmqgUBT3czb2u0=Erg@mail.gmail.com> <755100.21182.qm@web31816.mail.mud.yahoo.com>
Date: Wed, 01 Jun 2011 09:48:35 -0700
Message-ID: <BANLkTimLWTs6O0USR-MyFD2Hs6aURAygiOi6iHPXektKvc6n=g@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: "William J. Mills" <wmills@yahoo-inc.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Text for Native Applications
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2011 16:48:41 -0000

On Wed, Jun 1, 2011 at 9:11 AM, William J. Mills <wmills@yahoo-inc.com> wrote:
>> - native apps always use the authorization code grant
>
> I don't like this if it means I can't use passwrd grant for stuff like IMAP
> clients.

Sorry, didn't mean to suggest that password grants would go away.  The
business need is clearly there, no sense in forbidding it if people
are going to do it anyway. =)

v2.39.1 | Report a Bug | By Email | System Status