[OAUTH-WG] User Story - User Denying access.
Paul Lindner <lindner@inuus.com> Mon, 15 March 2010 20:42 UTC
Return-Path: <lindner@inuus.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 482313A6824 for <oauth@core3.amsl.com>; Mon, 15 Mar 2010 13:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.438
X-Spam-Level:
X-Spam-Status: No, score=0.438 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 Hmr3nSJlqqdv for <oauth@core3.amsl.com>; Mon, 15 Mar 2010 13:42:15 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id 83FC93A67EB for <oauth@ietf.org>; Mon, 15 Mar 2010 13:42:11 -0700 (PDT)
Received: by pvh1 with SMTP id 1so1186232pvh.31 for <oauth@ietf.org>; Mon, 15 Mar 2010 13:42:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.151.18 with SMTP id y18mr6041044wfd.338.1268685735986; Mon, 15 Mar 2010 13:42:15 -0700 (PDT)
Date: Mon, 15 Mar 2010 13:42:15 -0700
Message-ID: <b71cdca91003151342q760a6398m65a51557cafeec75@mail.gmail.com>
From: Paul Lindner <lindner@inuus.com>
To: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000e0cd328bea007100481dcea09"
Subject: [OAUTH-WG] User Story - User Denying access.
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, 15 Mar 2010 20:42:16 -0000
While considering what goes into OAuth 2.0 I'd like to incorporate this user story: Application redirects user to Authorization page. User presses [Cancel|Deny| etc.] In this case the behavior is undefined by the spec. In actual practice we have: * Twitter redirect to the callback URL with a denied GET parameter * Hyves sends back an access token with an error property and a request URL * LinkedIn redirects the user to a specific App-supplied URL. It seems that redirecting and setting error states from the OAuth Error Reporting extension would be the best way to go. Thoughts?
- [OAUTH-WG] User Story - User Denying access. Paul Lindner