Difference between revisions of "Purpose for Access Request"
From MgmtWiki
(→Taxonomy) |
(→JAR) |
||
| Line 20: | Line 20: | ||
These are all call [[Authorization]] Requests rather than Access Requests, which is the typical current transaction type. | These are all call [[Authorization]] Requests rather than Access Requests, which is the typical current transaction type. | ||
===JAR=== | ===JAR=== | ||
| + | [https://datatracker.ietf.org/doc/html/rfc9101 The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request] IETF RFC 9102(2022-21-08} | ||
| + | |||
===PAR=== | ===PAR=== | ||
===RAR=== | ===RAR=== | ||
Revision as of 15:03, 14 July 2022
Contents
Full Title
This is a discussion of the purpose for which a Relying Party or Verifier is requesting User Private Information.
Context
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:
- The sort of transaction for which data is required.
- Any information required to complete the transaction and whether it is to be retained by the verifier.
- Any optional information that the verifier wishes that is not required by the immediate transaction.
- It is the responsibility of the User Agent to:
- Display the information to the holder in a language that the user can understand.
- Input the holder's response
Taxonomy
- 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.
JAR
The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request IETF RFC 9102(2022-21-08}
