[OAUTH-WG] Re: RAR's equivalent of insufficient_scope
Vladimir Dzhuvinov / Connect2id <vladimir@connect2id.com> Fri, 17 January 2025 07:31 UTC
Return-Path: <vladimir@connect2id.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 380BEC1D6217 for <oauth@ietfa.amsl.com>; Thu, 16 Jan 2025 23:31:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.803
X-Spam-Level:
X-Spam-Status: No, score=-2.803 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=connect2id.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TRFQItziVDMY for <oauth@ietfa.amsl.com>; Thu, 16 Jan 2025 23:31:16 -0800 (PST)
Received: from mout-b-203.mailbox.org (mout-b-203.mailbox.org [195.10.208.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35A1AC1840E0 for <oauth@ietf.org>; Thu, 16 Jan 2025 23:31:15 -0800 (PST)
Received: from smtp1.mailbox.org (smtp1.mailbox.org [IPv6:2001:67c:2050:b231:465::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-b-203.mailbox.org (Postfix) with ESMTPS id 4YZBHJ6GSpz9vkm for <oauth@ietf.org>; Fri, 17 Jan 2025 08:31:08 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=connect2id.com; s=MBO0001; t=1737099068; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=KvtGRjSz7IHF5ivynOQWfSsQzH/IaM8lIPc9TyXwNY0=; b=d8CqAcYiAS/1x+Wyd0QPxs1bYEAmB47Y0X4bcsIZwGCdKMprzfzsk9fFAj3fcL9eHdvjAE j8G4vXI3z7vAMtjSoXRWsFdydECmximMhvkbrdFv5iw3ha/B+k8Ik6C0GtlIU1yHNxQMit mlUrAOkQMqW6lgpQPDIZqQHXsHIWnSYveN1MQrSvlio6nwIW4nDhEbZd7m+QzHPAISkZY0 kb5qpMi+j5jo5ni1t65lRqdNS63VnGVdGXH4oEcu5hy2WkKbsiljKfIIz3nzy4AMb5Uxgo fLnEIgqB70yT5ovQnjGnDE/QwsOwKpzmPPEZwWUK+8MmmNah27oH5pLWIiQF5A==
Content-Type: multipart/alternative; boundary="------------EF5iynB8FAXHSvwnWccBCr23"
Message-ID: <e18b71ac-cf3f-4735-babb-c9351f03b84b@connect2id.com>
Date: Fri, 17 Jan 2025 09:31:07 +0200
MIME-Version: 1.0
To: oauth@ietf.org
References: <CAOtx8DmtKmk1kuvFMDTDfif_qKWu+buC1-ZtmH-dHjhPuHwkmQ@mail.gmail.com>
From: Vladimir Dzhuvinov / Connect2id <vladimir@connect2id.com>
Content-Language: en-US
Organization: Connect2id Ltd.
In-Reply-To: <CAOtx8DmtKmk1kuvFMDTDfif_qKWu+buC1-ZtmH-dHjhPuHwkmQ@mail.gmail.com>
X-Rspamd-Queue-Id: 4YZBHJ6GSpz9vkm
Message-ID-Hash: 3N6RKDFBB3GFZ22QVCRHOBR5DYAPMMQJ
X-Message-ID-Hash: 3N6RKDFBB3GFZ22QVCRHOBR5DYAPMMQJ
X-MailFrom: vladimir@connect2id.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-oauth.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [OAUTH-WG] Re: RAR's equivalent of insufficient_scope
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/ahZrmrgaKcMhbp-6q5qneEE6YwY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Owner: <mailto:oauth-owner@ietf.org>
List-Post: <mailto:oauth@ietf.org>
List-Subscribe: <mailto:oauth-join@ietf.org>
List-Unsubscribe: <mailto:oauth-leave@ietf.org>
> insufficient_scope > The request requires higher privileges than provided by the > access token. The resource server SHOULD respond with the HTTP > 403 (Forbidden) status code and MAY include the "scope" > attribute with the scope necessary to access the protected > resource. "insufficient_scope" should be perfectly fine for "RAR-red" tokens. The error description is the token not having enough privileges, in the general sense. Do you need to communicate additional error info back from the resource? Vladimir Dzhuvinov On 17/01/2025 07:21, Dmitry Telegin wrote: > RAR does not define it's equivalent of RFC 6750's "insufficient_scope" > error response (could be "insufficient_authorization", for example). > Is this intentional? If not, would it make sense to define it in a > separate document? > > Dmitry > > _______________________________________________ > OAuth mailing list --oauth@ietf.org > To unsubscribe send an email tooauth-leave@ietf.org
- [OAUTH-WG] RAR's equivalent of insufficient_scope Dmitry Telegin
- [OAUTH-WG] Re: RAR's equivalent of insufficient_s… Vladimir Dzhuvinov / Connect2id
- [OAUTH-WG] Re: RAR's equivalent of insufficient_s… Dmitry Telegin