Difference between revisions of "Purpose for Access Request"

From MgmtWiki
Jump to: navigation, search
(Current Standard Request Messages)
(W3C Data Privacy Vocabulary)
Line 29: Line 29:
==W3C Data Privacy Vocabulary==
==W3C Data Privacy Vocabulary==
* [https://w3c.github.io/dpv/dpv/#vocab-purpose Collected sources]
* [https://w3c.github.io/dpv/dpv/#Purpose Data elements defined in the DPV]
[[Category: Consent]]
[[Category: Consent]]

Revision as of 08:34, 16 July 2022

Full Title

This is a discussion of the purpose for which a Relying Party or Verifier is requesting User Private Information.


The goal of this discussion is the creation of a display to the holder of a request for some details needed to create a transaction between the holder and the Verifier.

  • The request must reflect:
  1. The sort of transaction for which data is required.
  2. Any information required to complete the transaction and whether it is to be retained by the verifier.
  3. Any optional information that the verifier wishes that is not required by the immediate transaction.
  1. Display the information to the holder in a language that the user can understand.
  2. Input the holder's response


  • Holder
  • User Agent
  • Verifier

Current Standard Request Messages

These are all call Authorization Requests rather than Access Requests, which is the typical current transaction type.


The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request IETF RFC 9102(2021-08-21]


OAuth 2.0 Pushed Authorization Requests 2021-09 IETF RFC 9126
This document defines the pushed authorization request (PAR) endpoint, which allows clients to push the payload of an OAuth 2.0 authorization request to the authorization server via a direct request and provides them with a request URI that is used as reference to the data in a subsequent call to the authorization endpoint.


OAuth 2.0 Rich Authorization Requests draft-ietf-oauth-rar-12 2022-05-05

W3C Data Privacy Vocabulary