IETF Logo Mail Archive

Re: [OAUTH-WG] An access token claim to identify data processing purposes

Steinar Noem <steinar@udelt.no> Mon, 04 April 2022 14:33 UTC

Return-Path: <steinar@udelt.no>
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 E4E9C3A0A8B for <oauth@ietfa.amsl.com>; Mon, 4 Apr 2022 07:33:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=udelt-no.20210112.gappssmtp.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 G2ES4099LDQk for <oauth@ietfa.amsl.com>; Mon, 4 Apr 2022 07:33:16 -0700 (PDT)
Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (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 90A703A08D0 for <oauth@ietf.org>; Mon, 4 Apr 2022 07:32:59 -0700 (PDT)
Received: by mail-lf1-x133.google.com with SMTP id y32so2404952lfa.6 for <oauth@ietf.org>; Mon, 04 Apr 2022 07:32:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=udelt-no.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+7zwehYyha2rk/0X4Fn9Vdes6jVOuBaR0uJMNSmptJc=; b=ug2bMxhRz7NDM2QSuGcN0+eBcSDh6QHZNtL3GDNnEqqePLoOQyGAzxEs/+nOZZxv8P ASID7cLE1uIKOdNghoAJVlPPceayh4lBwAsu/dbu/jRz1dtc46AYQFeWKFcH++VWsJHE MEV3YbR+1lZVjIRoIf24yV3bYqItwfZDK7CjkJ4EKxIzrp6xhLoG2rQqbOYIN7GxxkM0 n3NZc1Q+zGs0LqGdS5nQbO2jC9gT4ixm6sNp0rtpf66jUNj2EzA3fl/a0xFFZWYpm2kB Ag9Bc8uOCERxoIJfhfNKVfd4HRtODY4TH2SsWtwYxDcnKsINqmLF465h+bgJ+Kt0U1Ss aZ9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+7zwehYyha2rk/0X4Fn9Vdes6jVOuBaR0uJMNSmptJc=; b=jlEo40eoZZwRtC3sVPCFeUx0KIpqkrcKCgjEY3zs6q7peyPQpD6SWdYLQrwYOWII+0 rqKtTwYpKLaX26zIGroZFuNsDQkGzk5qroiqjbPJK5a/B0zoewkPD5YMJpVMbTg5O05v 6xUz63xqHTKDI+uWlKD0HgSVQk94YXFNpymOR1PM3Caxg95CDVDPFu9wptbf68E9LZfu OSaX4Lls6c8EE58AuGOhqa1ikIFDRsb4lglJNkV5ECk7jCSS+LvfflmzwbckyIoRHPcl pvqEf0Ch6JjbBeMCHYWY2RFhNyaDmVnY28Lcf5gSqcj/J0w/aSzvMe29rHtfM45WzpKC BeYw==
X-Gm-Message-State: AOAM530hPhLkBQUBJgecCPa8gn/j8Xy4JjjmWWPIKm6dj0ruXBh3YFXJ u+yZFQ6NIVJklylbSBkEd15k49DF231/Zk+xK5ptbw==
X-Google-Smtp-Source: ABdhPJyCuH3bheqkzM+iRqFD7WSoep5I/doEjbglYq4yBogmSTPeTig+d9vuECiaF2p5Gg7WnJOJzZpxXnSwP2yo+cU=
X-Received: by 2002:a05:6512:3b27:b0:44a:c200:61e0 with SMTP id f39-20020a0565123b2700b0044ac20061e0mr18425954lfv.648.1649082776806; Mon, 04 Apr 2022 07:32:56 -0700 (PDT)
MIME-Version: 1.0
References: <CAP9qbHWPfswiPFhi4ijiYO8BcFJagWHROgBtqVZzB7zghdCzsg@mail.gmail.com>
In-Reply-To: <CAP9qbHWPfswiPFhi4ijiYO8BcFJagWHROgBtqVZzB7zghdCzsg@mail.gmail.com>
From: Steinar Noem <steinar@udelt.no>
Date: Mon, 04 Apr 2022 16:32:45 +0200
Message-ID: <CAHsNOKd3xe4EmhJvdGGE5V4fpq=sY0gWUvYJaGiMnVsrv7q-Dg@mail.gmail.com>
To: Roberto Polli <robipolli@gmail.com>
Cc: Giuseppe De Marco <giuseppe.demarco@teamdigitale.governo.it>, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001dfe4305dbd501e0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/GKDsn1iN0sa5P9N8T2LaqOryIMs>
Subject: Re: [OAUTH-WG] An access token claim to identify data processing purposes
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, 04 Apr 2022 14:33:21 -0000

Maybe you’ll find the work on RAR and identity assurance in OIDF
interesting?
RAR could be used for indicating a “legitimate interest”, and IA could
cater for accountability.

man. 4. apr. 2022 kl. 15:36 skrev Roberto Polli <robipolli@gmail.com>:

> Hi folks,
>
> I'm finding a standard way to express data processing purposes in access
> token/requests.
> E.g an access token request/response should provide an identifier linked
> to the reason that motivates
> a specific data processing.
>
> The first idea is that this identifier is conveyed in a custom claim,
> but maybe there's an existing claim/access token request parameter already.
>
> If such a parameter does not exist, which is the procedure for registering
> it?
>
> Kind regards,
> R:
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
-- 
Vennlig hilsen

Steinar Noem
Partner Udelt AS
Systemutvikler

| steinar@udelt.no | hei@udelt.no  | +47 955 21 620 | www.udelt.no |

v2.23.0 | Report a Bug | By Email