[OAUTH-WG] Client Metadata for Resource Indicators for OAuth 2.0
Filip Skokan <panva.ip@gmail.com> Sun, 30 June 2019 09:06 UTC
Return-Path: <panva.ip@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 6B718120073 for <oauth@ietfa.amsl.com>; Sun, 30 Jun 2019 02:06:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.737
X-Spam-Level:
X-Spam-Status: No, score=-1.737 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 iS0oyXXisE6w for <oauth@ietfa.amsl.com>; Sun, 30 Jun 2019 02:06:28 -0700 (PDT)
Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (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 749A1120071 for <oauth@ietf.org>; Sun, 30 Jun 2019 02:06:28 -0700 (PDT)
Received: by mail-oi1-x22f.google.com with SMTP id m206so7563491oib.12 for <oauth@ietf.org>; Sun, 30 Jun 2019 02:06:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=f4VSGSZhuxJEkvkmWIgyfi9yxwSxAmCBLEUt18D5BkU=; b=lcagUKISwiEdudffaLOQpmajH8w3xP6aAThMrO4L/Rmm5JmUl4sxHLaOBnpgMeMpvz xg39SV25S1tU1zBgYs3Is4vuLu1pb4YnXpN0OLde0HQwXObgWfyre9CUKzqHUs0X5J9Z ybBdmgvjgTmdEgXXQUFXMvbtLaOu5hC0eKSSjc7mImkt16hfZ24Vo6mr5iSfVAnyo1CN /5CqahQoifbx54m6VONoFHUZAhBZh+e0Tl5t3rjlbbkdYnWnmCqCmqI1+EcfB7lClTac mifMELQOQdoe4ZJc5FWX3o6OK6+p13QpH1yYCjG7ojHf9Vk9EGP1JG2xrq1euPTJbAyc LN/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=f4VSGSZhuxJEkvkmWIgyfi9yxwSxAmCBLEUt18D5BkU=; b=fu/er9uNWEhHw9WdUNAgZa/LhazvTqKNoNX/ue5w0vTYE6UF15p6CN7h3sIWz0vq/r rmsp6VPtJnS1ECe3IlHSHrFbZhOWiTFgz1rD0qIjSnlHp8WE8nYlNNV7Fkbz6wAg050J uzuIMIe6iTxm4TIZdNjbFDEENMY54BweGvgPekf10KSZj/Cf8jT/P4eujvvWjl2qm4hN 0PXCYqh6Q7N//d8IMqiy9C5sEk0JLYP9lgFnnaFloQelYHjQSx31pyEDhwdrhl1EL/bV 6lq9xZ4rfJ2JzcBUla3d84YmqB65cDoUBsKST+TKq3LbItD8S8tB0NnSpmroT7eehriA 5mQQ==
X-Gm-Message-State: APjAAAVcxROi+AQbJJIDg0H0LUoL+G/47Jzu8R5lBbshDp5C7yJ3TB6U HvO4oZC6YmBvak4rjj51frvx1NDvdR76WTHH07S8LkU=
X-Google-Smtp-Source: APXvYqwv15xwk0tqbw83jKZiJO3FuzpA0r6ggks9cwJuPLXvomOcgK3Yz9TJh7A9eeTNQgl3wKbyNCrqP+FqeovE4fw=
X-Received: by 2002:aca:f1c4:: with SMTP id p187mr3281738oih.149.1561885587487; Sun, 30 Jun 2019 02:06:27 -0700 (PDT)
MIME-Version: 1.0
From: Filip Skokan <panva.ip@gmail.com>
Date: Sun, 30 Jun 2019 11:06:16 +0200
Message-ID: <CALAqi_8wMUH+inZOuyus2277j9uHZCMQBZ28NTRGq6UcgeO1-g@mail.gmail.com>
To: oauth <oauth@ietf.org>, Brian Campbell <bcampbell@pingidentity.com>, John Bradley <jbradley@yubico.com>
Content-Type: multipart/alternative; boundary="0000000000009f4df4058c86d39c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/yrB5QjT4Z76YA2e7C9pATwaEDCI>
Subject: [OAUTH-WG] Client Metadata for Resource Indicators for OAuth 2.0
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: Sun, 30 Jun 2019 09:06:30 -0000
Dear John, Brian, everyone, I'd like to forward a request from several developers using my AS software to have defined client metadata property similar to scope in section 2 of RFC 7591 <https://tools.ietf.org/html/rfc7591#section-2> but for "resources a client must stay within the bounds of". My answer to these developer is that they are able to configure their AS with custom client metadata with defined validations executed *but since this is a re-occurring request I wonder if it would be worth to define and register a property in the resource indicators specification itself that would promote interoperability and would allow its readers to know what to look for in available client metadata.* The format can either be an array of resource values or just like with scope a space-delimited string of resource values. Best, *Filip Skokan*
- [OAUTH-WG] Client Metadata for Resource Indicator… Filip Skokan