Re: [OAUTH-WG] Tenancy in OAuth

Vladimir Dzhuvinov <vladimir@connect2id.com> Thu, 14 January 2021 20:20 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 9D20F3A162D for <oauth@ietfa.amsl.com>; Thu, 14 Jan 2021 12:20:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.178
X-Spam-Level:
X-Spam-Status: No, score=-2.178 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 i6zG6hsS2f8i for <oauth@ietfa.amsl.com>; Thu, 14 Jan 2021 12:20:29 -0800 (PST)
Received: from p3plsmtpa07-04.prod.phx3.secureserver.net (p3plsmtpa07-04.prod.phx3.secureserver.net [173.201.192.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AC323A162C for <oauth@ietf.org>; Thu, 14 Jan 2021 12:20:29 -0800 (PST)
Received: from [192.168.88.250] ([94.155.17.31]) by :SMTPAUTH: with ESMTPSA id 096YlhKyMCcJR096Zlc8Iu; Thu, 14 Jan 2021 13:20:28 -0700
X-CMAE-Analysis: v=2.4 cv=Bv5Yfab5 c=1 sm=1 tr=0 ts=6000a78c a=+I3yL00+yDwT8KNLgfs+4A==:117 a=+I3yL00+yDwT8KNLgfs+4A==:17 a=q0rX5H01Qin5IyBaTmIA:9 a=r77TgQKjGQsHNAKrUKIA:9 a=48vgC7mUAAAA:8 a=UqCG9HQmAAAA:8 a=OPE_keaqAAAA:8 a=__SxRlIrAAAA:8 a=IzNHE0-dzueNqnZ0qosA:9 a=QrD5s1Yyd6gXmrxS:21 a=czHfMAbg24kHEzhe:21 a=QEXdDO2ut3YA:10 a=y5F7X6vxnMXjTaPbyQcA:9 a=jJ4LBlMIXxj5INpu:21 a=k8IHbTIy_nNptCPv:21 a=y-bpsXK2LnFRJf2F:21 a=_W_S_7VecoQA:10 a=D8lnhvtxf0AONpHuB7QA:9 a=ZVk8-NSrHBgA:10 a=30ssDGKg3p0A:10 a=w1C3t2QeGrPiZgrLijVG:22 a=L47nHB812nP-ulAiFgtB:22 a=H5r4HjhRfVyZ-DhAOYba:22
X-SECURESERVER-ACCT: vladimir@connect2id.com
To: oauth@ietf.org
References: <35A2B178-B99F-4EBB-A2A8-A386183682C5@mendix.com>
From: Vladimir Dzhuvinov <vladimir@connect2id.com>
Autocrypt: addr=vladimir@connect2id.com; prefer-encrypt=mutual; keydata= mQENBFQZaoEBCACnP2YMDex9fnf+niLglTHGKuoypUSVKPQeKDHHeFQVzhRke+HBEZBwmA9T kZ+kEhyrNqibDPkPYVPmo23tM8mbNcTVQqpmN7NwgMpqkqcAqNsIyBtt09DjWOQVm57A3K+y uXI7SdNErdt79p2xQseOhqSC9+LgWuyh+mZsl2oFD4glFFfKSCMp2jATXrAMeGzigTnW+Xe0 tRzrwFN9zqykKxhUq9oHg1cNvoDtfxgsc9ysVHbxM/PM8o9lgj3YTQwKMBcCFclTqohji7ML fQ08eQo+acKTwC1WRzeLt9PknGt3C4TmvdCl0c1BQTTTNiF96Hu4kbaiBIbsfxJOR8+VABEB AAG0LFZsYWRpbWlyIER6aHV2aW5vdiA8dmxhZGltaXJAY29ubmVjdDJpZC5jb20+iQE+BBMB AgAoBQJUGWqBAhsjBQkJZgGABgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRAZ0vUyOqri Ql62B/wOO0s2JC/QvO6w9iSsRhCOa/JZi+wO+l01V7eGCQ1cYf1W26Y7iKiUlY4/Kz+cr69D pMtkv3UpDTGejKEfspLUxz5Vo3T4oAKbTtNtVIZL/XxH3/JhJ719Jj4eLoe9/djKkGYTX2O5 bMk8TpO1DDjbIw4r9XKI9ZIk96zlKnZvrg7Ho7oOl0ZIf8AzcvdqZEUogDwyr8uwOU+jIyux mOTthepBzXCNjjBjnc8I1//9YppAIaGJ5nnXelVVD1/dyOszogervzFNANEIOvNvCd9G5u4e s7qkDKWKY7/Lj1tF+tMrDTrOh6JqUKbGNeTUB8DlPvIoNyqHUYfBELdpw1Nd
X-Enigmail-Draft-Status: N11100
Organization: Connect2id Ltd.
Message-ID: <ae0c1d64-b9c1-738c-a0a9-67f3ed310af4@connect2id.com>
Date: Thu, 14 Jan 2021 22:20:26 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <35A2B178-B99F-4EBB-A2A8-A386183682C5@mendix.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms040208070303010003020102"
X-CMAE-Envelope: MS4xfARSCP75CF2eGFMimUOsRO4DAOGsUU6Gt1brBk1E4un2Y+lNELeMBBWiRwmLIow7o+1xrU4X3nBB2q3hrjdfBzfLbUN9DrW2DT5nG8tc2sgLHMg0wZP4 eksP3PKdpVuoL/Th9QrBRpuXPkdazahwT8NSe0JX1+8QMDTmqLZReb0ki2Dh6RO9UrxqztAudeGNrA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/MIuhrRGS6D45Oxd45ikrG6rB9e0>
Subject: Re: [OAUTH-WG] Tenancy in OAuth
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: Thu, 14 Jan 2021 20:20:33 -0000

On 13/01/2021 12:10, Jaap Francke wrote:
> Thanks Justin and Vladimir for your guidance!
>
> The resource indicator approach seems to have the best fit for my use case.
> It addresses my coarse/mid-grained use case, without bringing the complexity of the fine-grained RAR approach.
> Encoding the tenant into scope values remains an option as well.
> Ensuring the token validation is implemented properly is indeed a point of attention.
>
> Meanwhile I've been looking into OAuth/OIDC specs for client registration. 
> It may also be useful to extend the client's metadata with 'resource' to bind the specific client to a specific tenant(s).
> Would that make sense to you as well?

If that make sense in your scenario, then why not. We have the "scope"
client metadata field, which was intended for that purpose, but relating
to the scope authZ parameter.

https://tools.ietf.org/html/rfc7591#section-2

>    scope
>       String containing a space-separated list of scope values (as
>       described in Section 3.3 <https://tools.ietf.org/html/rfc7591#section-3.3> of OAuth 2.0 [RFC6749 <https://tools.ietf.org/html/rfc6749>]) that the client
>       can use when requesting access tokens.  The semantics of values in
>       this list are service specific.  If omitted, an authorization
>       server MAY register a client with a default set of scopes.


Vladimir


>
> Great feedback, kind regards, 
> Jaap
>
>
> ´╗┐On 12/01/2021, 23:10, "OAuth on behalf of oauth-request@ietf.org" <oauth-bounces@ietf.org on behalf of oauth-request@ietf.org> wrote:
>
>     Send OAuth mailing list submissions to
>     	oauth@ietf.org
>
>     To subscribe or unsubscribe via the World Wide Web, visit
>     	https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Foauth&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383168168%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=zNVyuy2avEEWtIJ3eXZGEV9S0KLyYj27KiG2yOPtW9Q%3D&amp;reserved=0
>     or, via email, send a message with subject or body 'help' to
>     	oauth-request@ietf.org
>
>     You can reach the person managing the list at
>     	oauth-owner@ietf.org
>
>     When replying, please edit your Subject line so it is more specific
>     than "Re: Contents of OAuth digest..."
>
>
>     Today's Topics:
>
>        1. Re: Tenancy in OAuth (Justin Richer)
>        2. Re: Tenancy in OAuth (Vladimir Dzhuvinov)
>
>
>     ----------------------------------------------------------------------
>
>     Message: 1
>     Date: Tue, 12 Jan 2021 16:13:26 -0500
>     From: Justin Richer <jricher@mit.edu>
>     To: Jaap Francke <Jaap.Francke=40mendix.com@dmarc.ietf.org>
>     Cc: "oauth@ietf.org" <oauth@ietf.org>
>     Subject: Re: [OAUTH-WG] Tenancy in OAuth
>     Message-ID: <E3DE5ED2-7506-4090-A32A-F3D4AE797DF5@mit.edu>
>     Content-Type: text/plain; charset="utf-8"
>
>     Hi Jaap,
>
>     There have been a number of efforts to address this kind of thing in the OAuth world. You can definitely use a special scope to encode this value, which has the benefit of fitting into the implementation limitations of nearly all OAuth systems out there. The ?resource? parameter can also be used for the kind of thing, and it gives you a bucket that?s separate from ?scope? so that you can keep the latter available for describing the API itself:
>
>     https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc8707&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383168168%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=5clKn%2B8%2FCEiQindejfHncA670FWVoy%2BHDQ49JtOORjE%3D&amp;reserved=0 <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc8707&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383168168%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=5clKn%2B8%2FCEiQindejfHncA670FWVoy%2BHDQ49JtOORjE%3D&amp;reserved=0>
>
>     There?s also the Rich Authorization Request (RAR) draft that this group is currently working on, which provides a multi-dimensional way to describe access. It?s more complex than scopes, but it boils down to having JSON objects describe the elements needed. In this case you might put the API bits into the ?actions? and ?datatypes? fields, and put the tenant information into the ?locations? field. I believe there are people using it in exactly this way today:
>
>     https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-oauth-rar-03&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383168168%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=hxn2gFdUhhmWrf0ATaqUUUB9C62yh%2FY27aNOvR1hWbM%3D&amp;reserved=0 <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-oauth-rar-03&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383168168%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=hxn2gFdUhhmWrf0ATaqUUUB9C62yh%2FY27aNOvR1hWbM%3D&amp;reserved=0>
>
>     There are also some historical efforts to address this, including an ?audience? and a (completely separate) ?aud" parameter, but AFAIK neither of these have been raised to standard or even to common practice, and so I wouldn?t recommend it. I currently have a project to migrate a system that?s currently using one of these onto RAR.
>
>      ? Justin
>
>     > On Jan 12, 2021, at 11:20 AM, Jaap Francke <Jaap.Francke=40mendix.com@dmarc.ietf.org> wrote:
>     > 
>     > Hi,
>     >  
>     > I?m looking into the topic of tenancy. A multi-tenant service can be considered as an OAuth Resource Server managing resources of different tenants.
>     > An AS makes authorization decisions and communicates these using scopes, so one way would be to ?encode? the tenant into the scope values.
>     > Another line of thought is to somehow bind/restrict an acces-token to a certain tenant, leaving the set of scopes being used more static.
>     >  
>     > My question is whether this has been a topic that has been addressed in the OAuth working group? Any common practice or draft?
>     > Thanks in advance for your replies.
>     >  
>     > Kind regards,
>     >  
>     > Jaap Francke
>     > Product Manager Identity
>     > +31(0)641495324
>     > mendix.com <https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmendix.com%2F&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383168168%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=nPKjePc%2B%2B8TuM4zuCG6ZU2XNsPmJxu5WidmCHz9E%2BSU%3D&amp;reserved=0>
>     > <image001.png> <https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.mendix.com%2F&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383168168%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=7HQ1qe32Hc9QcYNVY8667ufxmLz7DDWCYA8mhsKSHVo%3D&amp;reserved=0>
>     >  
>     >  
>     > _______________________________________________
>     > OAuth mailing list
>     > OAuth@ietf.org <mailto:OAuth@ietf.org>
>     > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Foauth&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383168168%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=zNVyuy2avEEWtIJ3eXZGEV9S0KLyYj27KiG2yOPtW9Q%3D&amp;reserved=0 <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Foauth&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383168168%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=zNVyuy2avEEWtIJ3eXZGEV9S0KLyYj27KiG2yOPtW9Q%3D&amp;reserved=0>
>     -------------- next part --------------
>     An HTML attachment was scrubbed...
>     URL: <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fbrowse%2Foauth%2Fattachments%2F20210112%2F19aa55e2%2Fattachment.htm&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383168168%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=1QzWSxQ4esCxjTI6f5mb7CPFxiYs9aCdVcHIyEnuwMk%3D&amp;reserved=0>
>
>     ------------------------------
>
>     Message: 2
>     Date: Wed, 13 Jan 2021 00:10:01 +0200
>     From: Vladimir Dzhuvinov <vladimir@connect2id.com>
>     To: oauth@ietf.org
>     Subject: Re: [OAUTH-WG] Tenancy in OAuth
>     Message-ID: <cc41517f-f732-0d6f-95f3-64bb7fcdf24e@connect2id.com>
>     Content-Type: text/plain; charset="utf-8"
>
>     Hello Jaap,
>
>     Justin made a good overview of the available OAuth facilities when
>     dealing with multiple resource servers or resource server tenants.
>
>     If you have control over the resource server, i.e. the token validation
>     is going to happen in one place, then you have plenty of freedom to find
>     out what will work best for you, semantically and in terms of available
>     OAuth server.
>
>     In cases when the resources are left to implement the token validation
>     on their own my preferred approach is to encode the resource server
>     identity (tenant) into the scope values. Access is defined in one place
>     and I don't have to worry about the developer accidentally forgetting
>     the "resource" or "aud(ience)" check.
>
>     Vladimir
>
>
>     On 12/01/2021 23:13, Justin Richer wrote:
>     > Hi Jaap,
>     >
>     > There have been a number of efforts to address this kind of thing in
>     > the OAuth world. You can definitely use a special scope to encode this
>     > value, which has the benefit of fitting into the implementation
>     > limitations of nearly all OAuth systems out there. The ?resource?
>     > parameter can also be used for the kind of thing, and it gives you a
>     > bucket that?s separate from ?scope? so that you can keep the latter
>     > available for describing the API itself:
>     >
>     > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc8707&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383168168%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=5clKn%2B8%2FCEiQindejfHncA670FWVoy%2BHDQ49JtOORjE%3D&amp;reserved=0
>     >
>     > There?s also the Rich Authorization Request (RAR) draft that this
>     > group is currently working on, which provides a multi-dimensional way
>     > to describe access. It?s more complex than scopes, but it boils down
>     > to having JSON objects describe the elements needed. In this case you
>     > might put the API bits into the ?actions? and ?datatypes? fields, and
>     > put the tenant information into the ?locations? field. I believe there
>     > are people using it in exactly this way today:
>     >
>     > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-oauth-rar-03&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383168168%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=hxn2gFdUhhmWrf0ATaqUUUB9C62yh%2FY27aNOvR1hWbM%3D&amp;reserved=0
>     >
>     > There are also some historical efforts to address this, including an
>     > ?audience? and a (completely separate) ?aud" parameter, but AFAIK
>     > neither of these have been raised to standard or even to common
>     > practice, and so I wouldn?t recommend it. I currently have a project
>     > to migrate a system that?s currently using one of these onto RAR.
>     >
>     > ?? Justin
>     >
>     >> On Jan 12, 2021, at 11:20 AM, Jaap Francke
>     >> <Jaap.Francke=40mendix.com@dmarc.ietf.org
>     >> <mailto:Jaap.Francke=40mendix.com@dmarc.ietf.org>> wrote:
>     >>
>     >> Hi,
>     >> ?
>     >> I?m looking into the topic of tenancy. A multi-tenant service can be
>     >> considered as an OAuth Resource Server managing resources of
>     >> different tenants.
>     >> An AS makes authorization decisions and communicates these using
>     >> scopes, so one way would be to ?encode? the tenant into the scope values.
>     >> Another line of thought is to somehow bind/restrict an acces-token to
>     >> a certain tenant, leaving the set of scopes being used more static.
>     >> ?
>     >> My question is whether this has been a topic that has been addressed
>     >> in the OAuth working group? Any common practice or draft?
>     >> Thanks in advance for your replies.
>     >> ?
>     >> Kind regards,
>     >> *?*
>     >> *Jaap Francke*
>     >> Product Manager Identity
>     >> +31(0)641495324
>     >>
>     >> mendix.com <https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmendix.com%2F&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383178166%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=%2FAM7a7iH5y8E6ETAg%2BAmrNh3WnAuBiOZ%2FEBhikqOFxI%3D&amp;reserved=0>
>     >>
>     >> *<image001.png>* <https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.mendix.com%2F&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383178166%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=MaqH3Kv4ob56Lp28m9g2idLEXiLlpkkwt4QctYTAiqg%3D&amp;reserved=0>
>     >> *?*
>     >> ?
>     >> _______________________________________________
>     >> OAuth mailing list
>     >> OAuth@ietf.org <mailto:OAuth@ietf.org>
>     >> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Foauth&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383178166%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=8%2Fk%2BVZS9e%2B%2FCwEwSVo7nqivuwjdg3Jy48x6awkBTxV0%3D&amp;reserved=0
>     >
>     >
>     > _______________________________________________
>     > OAuth mailing list
>     > OAuth@ietf.org
>     > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Foauth&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383178166%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=8%2Fk%2BVZS9e%2B%2FCwEwSVo7nqivuwjdg3Jy48x6awkBTxV0%3D&amp;reserved=0
>
>     -- 
>     Vladimir Dzhuvinov
>
>     -------------- next part --------------
>     An HTML attachment was scrubbed...
>     URL: <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fbrowse%2Foauth%2Fattachments%2F20210113%2F136b5985%2Fattachment.htm&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383178166%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=0dJ3kYyigdBtbUDNhwRipAzwj5urzkKKLCzquGTy7vY%3D&amp;reserved=0>
>     -------------- next part --------------
>     A non-text attachment was scrubbed...
>     Name: smime.p7s
>     Type: application/pkcs7-signature
>     Size: 4007 bytes
>     Desc: S/MIME Cryptographic Signature
>     URL: <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fbrowse%2Foauth%2Fattachments%2F20210113%2F136b5985%2Fattachment.p7s&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383178166%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=%2BqMHy4Z%2FkjRCeyE8UHgUuqtm8D%2FLwPd2HffEmhiVfcs%3D&amp;reserved=0>
>
>     ------------------------------
>
>     Subject: Digest Footer
>
>     _______________________________________________
>     OAuth mailing list
>     OAuth@ietf.org
>     https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Foauth&amp;data=04%7C01%7Cjaap.francke%40mendix.com%7C93707202bd484789530008d8b746e1f4%7Cb4e3c78d8e3b46d8bc565540da23ba4d%7C0%7C0%7C637460862383178166%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=8%2Fk%2BVZS9e%2B%2FCwEwSVo7nqivuwjdg3Jy48x6awkBTxV0%3D&amp;reserved=0
>
>
>     ------------------------------
>
>     End of OAuth Digest, Vol 147, Issue 6
>     *************************************
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

-- 
Vladimir Dzhuvinov