IETF Logo Mail Archive

Re: [OAUTH-WG] Authorization request errors

Torsten Lodderstedt <torsten@lodderstedt.net> Wed, 04 July 2012 17:31 UTC

Return-Path: <torsten@lodderstedt.net>
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 B2F1921F876F for <oauth@ietfa.amsl.com>; Wed, 4 Jul 2012 10:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yoh1U5lBvGBX for <oauth@ietfa.amsl.com>; Wed, 4 Jul 2012 10:31:12 -0700 (PDT)
Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.31.25]) by ietfa.amsl.com (Postfix) with ESMTP id D790A21F8762 for <oauth@ietf.org>; Wed, 4 Jul 2012 10:31:11 -0700 (PDT)
Received: from [79.253.28.237] (helo=[192.168.71.42]) by smtprelay02.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1SmTQ9-0001R1-Qf; Wed, 04 Jul 2012 19:31:21 +0200
Message-ID: <4FF47DDD.3010904@lodderstedt.net>
Date: Wed, 04 Jul 2012 19:31:09 +0200
From: Torsten Lodderstedt <torsten@lodderstedt.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Jérôme LELEU <leleuj@gmail.com>
References: <CAP279LzK6LtYZRNU+vqP+NAYV2ehmeC6sdJ3f+EnpS5URZiV6w@mail.gmail.com>
In-Reply-To: <CAP279LzK6LtYZRNU+vqP+NAYV2ehmeC6sdJ3f+EnpS5URZiV6w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070104080701010803040506"
X-Df-Sender: dG9yc3RlbkBsb2RkZXJzdGVkdC1vbmxpbmUuZGU=
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] Authorization request errors
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, 04 Jul 2012 17:31:12 -0000

Hi Jerome,

I read the introduction of 4.1.2.1 as follows: The authorization server 
shall display an error message to the end-user. So no HTTP error code 
required.

best regards,
Torsten.

Am 21.06.2012 21:40, schrieb Jérôme LELEU:
> Hi,
>
> I'm trying to implement OAuth 2.0 provider support and, in particular, 
> right handling of errors.
>
> Following OAuth 2.0 spec : 
> http://tools.ietf.org/html/draft-ietf-oauth-v2-28, I don't understand 
> the authorization request errors : part 4.1.2.1.
> If I have a valid redirection url, I understand that an error should 
> be returned with GET parameters (error, error_description...) in the 
> redirected url as shown in example.
> But in case of invalid redirection url or unknown client_id (which 
> makes validation of redirection url impossible), what http code should 
> I return ? 500 ? 400 ? What should be the format of the error message 
> ? Json ? plaintext ? like a POST body ?
>
> I'm certainly misunderstanding OAuth spec, but I would appreciate any 
> help.
> Thanks.
> Best regards,
> Jérôme
>
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email