IETF Logo Mail Archive

Re: [OAUTH-WG] Throttling error using resource owner password credentials grant or authorization code grant

Justin Richer <jricher@mitre.org> Wed, 17 July 2013 17:55 UTC

Return-Path: <jricher@mitre.org>
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 5D57C21E804C for <oauth@ietfa.amsl.com>; Wed, 17 Jul 2013 10:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.448
X-Spam-Level:
X-Spam-Status: No, score=-6.448 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 C6MIKWRDxzq7 for <oauth@ietfa.amsl.com>; Wed, 17 Jul 2013 10:55:32 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 2C73721F9FCA for <oauth@ietf.org>; Wed, 17 Jul 2013 10:55:32 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 9C0E31F0B17; Wed, 17 Jul 2013 13:55:30 -0400 (EDT)
Received: from IMCCAS01.MITRE.ORG (imccas01.mitre.org [129.83.29.78]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 8E1981F0AF4; Wed, 17 Jul 2013 13:55:30 -0400 (EDT)
Received: from [10.146.15.13] (129.83.31.56) by IMCCAS01.MITRE.ORG (129.83.29.78) with Microsoft SMTP Server (TLS) id 14.2.342.3; Wed, 17 Jul 2013 13:55:30 -0400
Message-ID: <51E6DA30.1070909@mitre.org>
Date: Wed, 17 Jul 2013 13:53:52 -0400
From: Justin Richer <jricher@mitre.org>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Santiago Pérez <spmarin.tid@gmail.com>
References: <CAOrzMNZ_X6EsAAYOjeRrKBG_HDtSDZLLxhewLJ54u=DGEvwcYQ@mail.gmail.com>
In-Reply-To: <CAOrzMNZ_X6EsAAYOjeRrKBG_HDtSDZLLxhewLJ54u=DGEvwcYQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070907040003030200040509"
X-Originating-IP: [129.83.31.56]
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] Throttling error using resource owner password credentials grant or authorization code grant
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, 17 Jul 2013 17:55:37 -0000

Rate limiting an HTTP connection is not something OAuth-specific. HTTP 
error code "429 Too Many Requests" is probably your best bet for getting 
clients to behave:

http://tools.ietf.org/html/rfc6585#section-4

  -- Justin

On 07/16/2013 12:30 PM, Santiago Pérez wrote:
> Dear all,
>
> We are implementing a OAuth 2.0 server and there is a point that is 
> not clear for me in the RFC 6749.
>
> What error should we return when the maximum number of attempts for 
> resource owner credentials is exceeded? I can not see any suitable 
> error in the current RFC.
>
> We are implementing a policy for controlling this X attempts per 
> period (e.g.: 3 times/15 minutes)
>
> Thanks for your answer.
>
> Kind Regards,
>
> Santiago Pérez
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email