IETF Logo Mail Archive

Re: [OAUTH-WG] device profile comments

Marius Scurtescu <mscurtescu@google.com> Mon, 10 May 2010 18:07 UTC

Return-Path: <mscurtescu@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 B812A3A6C06 for <oauth@core3.amsl.com>; Mon, 10 May 2010 11:07:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.849
X-Spam-Level:
X-Spam-Status: No, score=-105.849 tagged_above=-999 required=5 tests=[AWL=0.128, 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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BhAMBSw7RIiD for <oauth@core3.amsl.com>; Mon, 10 May 2010 11:07:45 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 1F4843A6BF4 for <oauth@ietf.org>; Mon, 10 May 2010 11:06:48 -0700 (PDT)
Received: from wpaz33.hot.corp.google.com (wpaz33.hot.corp.google.com [172.24.198.97]) by smtp-out.google.com with ESMTP id o4AI6aBs030404 for <oauth@ietf.org>; Mon, 10 May 2010 11:06:36 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1273514796; bh=vhrwHOtnzPDEdjKYQwnn8m7z5g4=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type:Content-Transfer-Encoding; b=ozt5LZ8lg5r3N2LrxwUcbeCZrQhC+pz72LiDQNJwcFsevsSsOEo7ZnJDrR+gSj8/x MMOUWph8oM60PuQV0TxFg==
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:content-transfer-encoding:x-system-of-record; b=WRp/97BhNkGcygkc8HCiBmLTF1rl3EiZsA9iAUjnvn367eiuxTbkNKIHbH39f6U1Y aRhHjndM/k46eSwhFn9Sw==
Received: from pwj3 (pwj3.prod.google.com [10.241.219.67]) by wpaz33.hot.corp.google.com with ESMTP id o4AI6ZtS013691 for <oauth@ietf.org>; Mon, 10 May 2010 11:06:35 -0700
Received: by pwj3 with SMTP id 3so1778889pwj.22 for <oauth@ietf.org>; Mon, 10 May 2010 11:06:34 -0700 (PDT)
Received: by 10.140.252.10 with SMTP id z10mr2969180rvh.45.1273514794835; Mon, 10 May 2010 11:06:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.141.125.21 with HTTP; Mon, 10 May 2010 11:06:14 -0700 (PDT)
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343B3AB46E0B@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <i2odaf5b9571004221649h733f675bva2f9f4438ef43921@mail.gmail.com> <y2kfd6741651004221758y7d207961we2a6d1e65e6dd279@mail.gmail.com> <o2qdaf5b9571004262327u90caa8b6vbfa976ec44c86d91@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343B3AB46E0B@P3PW5EX1MB01.EX1.SECURESERVER.NET>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Mon, 10 May 2010 11:06:14 -0700
Message-ID: <AANLkTin2hddp-bnjJCuDOShuvk6Ti0t_cyraQebgFeO6@mail.gmail.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] device profile comments
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, 10 May 2010 18:07:46 -0000

On Sun, May 9, 2010 at 10:12 AM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
>
>> -----Original Message-----
>> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf
>> Of Brian Eaton
>> Sent: Monday, April 26, 2010 11:27 PM
>> To: David Recordon
>> Cc: oauth@ietf.org
>> Subject: Re: [OAUTH-WG] device profile comments
>>
>> New step E.
>>
>> "(E) After the end user grants or denies access, the Authorization Server
>> MAY redirect to a callback URL previously registered for the client.  If the user
>> denies access, the Authorization Server must append the query parameter
>> "error=user_denied" to the callback URL.
>> The callback URL can be used to provide further instructions to the user if
>> necessary."
>
> If the client can receive callbacks, why use this flow?

I think this is a generic callback page with information for this
specific class of devices. The device itself cannot receive callbacks.

Marius

v2.23.0 | Report a Bug | By Email