Re: [OAUTH-WG] Issue: 'username' parameter proposal

Evan Gilbert <uidude@google.com> Mon, 19 April 2010 15:53 UTC

Return-Path: <uidude@google.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C062728C290 for <oauth@core3.amsl.com>; Mon, 19 Apr 2010 08:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.872
X-Spam-Level:
X-Spam-Status: No, score=-101.872 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7HUzACRIfjXF for <oauth@core3.amsl.com>; Mon, 19 Apr 2010 08:53:58 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 2E62D28C216 for <oauth@ietf.org>; Mon, 19 Apr 2010 08:34:28 -0700 (PDT)
Received: from wpaz29.hot.corp.google.com (wpaz29.hot.corp.google.com [172.24.198.93]) by smtp-out.google.com with ESMTP id o3JFYIPj017311 for <oauth@ietf.org>; Mon, 19 Apr 2010 17:34:18 +0200
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1271691258; bh=PdUxA9LCAh4vZd1arSpNHgKLEhE=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=kY+GGvfQJcjVw2DEGGPiZUUgnT/ZjGfrv/WUsAfEXwdkiq3LvAVpaMVISf74XAfUk Z9y4sirVqwVp1IuOmSa6A==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:x-system-of-record; b=rIppFmNQIZsemF4a8ba7wQT/UM0Js45BvTvLdPqdOcObgv5eP6wAqg/G9VNXam0Pd pnfvafr4seSBK5ri6/pmA==
Received: from qyk32 (qyk32.prod.google.com [10.241.83.160]) by wpaz29.hot.corp.google.com with ESMTP id o3JFYG3h007157 for <oauth@ietf.org>; Mon, 19 Apr 2010 08:34:17 -0700
Received: by qyk32 with SMTP id 32so4725025qyk.12 for <oauth@ietf.org>; Mon, 19 Apr 2010 08:34:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.16.148 with HTTP; Mon, 19 Apr 2010 08:33:56 -0700 (PDT)
In-Reply-To: <C7ECAF46.3234F%eran@hueniverse.com>
References: <AcrczUP0fQn1S3ZSlkCeyUAs62ovDQ==> <C7ECAF46.3234F%eran@hueniverse.com>
From: Evan Gilbert <uidude@google.com>
Date: Mon, 19 Apr 2010 08:33:56 -0700
Received: by 10.229.193.18 with SMTP id ds18mr207036qcb.14.1271691256547; Mon, 19 Apr 2010 08:34:16 -0700 (PDT)
Message-ID: <r2pc8689b661004190833tf46085bayb92b840acf080bb4@mail.gmail.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: multipart/alternative; boundary="0016362845f49ca553048498b159"
X-System-Of-Record: true
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Issue: 'username' parameter proposal
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 19 Apr 2010 15:53:58 -0000

More details on this enhancement.

Goal: Make sure you get an access token for the right user in immediate
mode.

Use case where we have problems if we don't have username parameter:

   1. Bob is logged into a web site as bob@IDP.com.
   2. Mary (his wife) is logged into IDP on the same computer as
   mary@IDP.com
   3. A request is made to get an access token via the User-Agent flow in
   immediate mode (or with any redirect without prompting the user)
   4. -ob now has an access token for Mary and (posts activities, schedules
   events, gets contacts) as Mary
   5. Hilarity ensues


Secondary goal: Provide a hint for non-immediate mode

On Thu, Apr 15, 2010 at 11:55 AM, Eran Hammer-Lahav <eran@hueniverse.com>wrote:

> Evan Gilbert proposed a 'username' request parameter to allow the client to
> limit the end user to authenticate using the provided authorization server
> identifier. The proposal has not been discussed or supported by others, and
> has not received a security review.
>
> Proposal: Obtain further discussion and support from others, as well as a
> security review of the proposal. Otherwise, do nothing.
>
> EHL
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>