Re: [OAUTH-WG] Device Authorization Grant Interval

Janak Amarasena <janakama360@gmail.com> Mon, 03 June 2019 16:54 UTC

Return-Path: <janakama360@gmail.com>
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 943A512067F for <oauth@ietfa.amsl.com>; Mon, 3 Jun 2019 09:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level:
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KYPL0-j95GTe for <oauth@ietfa.amsl.com>; Mon, 3 Jun 2019 09:54:56 -0700 (PDT)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5297612069E for <oauth@ietf.org>; Mon, 3 Jun 2019 09:54:56 -0700 (PDT)
Received: by mail-wm1-x32b.google.com with SMTP id f10so11980954wmb.1 for <oauth@ietf.org>; Mon, 03 Jun 2019 09:54:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KB21V2+CmqUc2ezlvACQs+bumc8TTHl7ydaOOcNg/Og=; b=JsHPPDr384vMBM1BerB5dN3bLH4dnvRLFTlChGrba1LfWYBkW7bH2IhYwqQlCaK3hP Sbfj9es4Ud7vgePshzy2dFyZFdJt1j+OGiFUa2UUV0EO/wHRm5zGYBKNzUVxkSkIajsc w3ZQCYsXR+t9KZQ5XSfXSxhBZ1PgC1kjhR+oVBzAXHKtMJyROXkcJziYIn1uc9Ttad9I P5OKQEYJZ/ptFm9tglVWXvfER6HP2sOiiQSrd+i8czrHlwTVCvzyoaV2uYjWH4yHct44 MT6qGyQWzQdAdRZ+QramK7B3tYqphVafhD0evQprxR6qX4ud+uPxqels9ZmXkOhRTFGq a0LA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KB21V2+CmqUc2ezlvACQs+bumc8TTHl7ydaOOcNg/Og=; b=okOaZfy0A8FE5iHI9ZC+DZm6CONTvqrrE5CI97vo8Nk0gkLjjsKUz3yLlKYePH7a// IQmkzSGhefMu+rbXCLoCm2bdyL7RO9A624Ou0KEu89Y9qj7/irbpfRgjo6lK/hMEeQtA ErUYXH8E1OYekrmUC9YsdITICU6nzpwUb3mnKhFBNnK1/wCfgVG4jKcpfr2HhYd60wMV +dwj8uClDyea8/KMJd+tQrUbwZ8ASCKyyxe9vjN3LnohiORjLfaTpg/oWcsTh+rUktkf 1Z3H34z6Gp5TcBHsL5znBFvGVZ4sDczG9qlbxCwAu0dNG74R+PSFKma6jJvpKEZ5gg0v 5p/Q==
X-Gm-Message-State: APjAAAUmN/HYN8RgJrXKQ9muFM/JEddsAwN4yS02yCOsX8LNHYiIFb0b iOrHnmzhiUflpA+XnyV+cvXyB7/9OqDRXdBT274ong==
X-Google-Smtp-Source: APXvYqwB7zLW/bFmBUwwcMrD85N37J31MN6TRt69TsZyOrtGTHaNwR33wVsl7Efqp+kCn2MdxSI3JJAp0a7hLAtGduc=
X-Received: by 2002:a1c:9813:: with SMTP id a19mr14816054wme.11.1559580894843; Mon, 03 Jun 2019 09:54:54 -0700 (PDT)
MIME-Version: 1.0
References: <CAM7dPt0nS=+6oACUTc=sXnw3dpEqMB3ETq03iYnM1HsLv2_OQg@mail.gmail.com> <CE182107-09A2-49EB-9CBD-7354F051D2FA@authlete.com>
In-Reply-To: <CE182107-09A2-49EB-9CBD-7354F051D2FA@authlete.com>
From: Janak Amarasena <janakama360@gmail.com>
Date: Mon, 03 Jun 2019 22:24:45 +0530
Message-ID: <CAM7dPt2C=xnpXySpJnPW4vBGX-B4Nmnsthbxtvx+yPqMQXviKQ@mail.gmail.com>
To: Joseph Heenan <joseph@authlete.com>
Cc: oauth@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003c5700058a6e3950"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/4xxMQvifniFd7-SRrFsZ2qhSWXw>
Subject: Re: [OAUTH-WG] Device Authorization Grant Interval
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 03 Jun 2019 16:54:59 -0000

Hi Joseph,

Thank you for the information, this what I was also thinking. It would be
nice if this can be defined in the specification itself, maybe as a
recommendation as there can be wrongly written client applications or even
if some party is trying to do a brute force attack.

Best Regards,
Janak

On Sun, Jun 2, 2019 at 1:40 PM Joseph Heenan <joseph@authlete.com> wrote:

> Hi Janak,
>
> Interestingly this came up when discussing the CIBA specification (which
> builds upon device authorization grant to some extent) recently:
> https://bitbucket.org/openid/mobile/issues/135/token-endpoint-response-when-client-polls
>
> The thought that group came up with is that returning ‘invalid_request’
> would be appropriate - ideally appropriate error_description to make it
> easy to understand what’s going on.
>
> Cheers,
>
> Joseph
>
>
> > On 21 May 2019, at 06:21, Janak Amarasena <janakama360@gmail.com> wrote:
> >
> > Hi all,
> >
> > In the OAuth2 Device Authorization Grant, what would be an appropriate
> response if the client does not respect the set polling interval and keeps
> on polling with a lower interval?
> >
> > Thank you,
> > Best Regards,
> >
> > Janak Amarasena
> > _______________________________________________
> > OAuth mailing list
> > OAuth@ietf.org
> > https://www.ietf.org/mailman/listinfo/oauth
>
>