Difference between revisions of "Purpose for Access Request"
From MgmtWiki
(→Current Standard Request Messages) |
(→Context) |
||
| Line 8: | Line 8: | ||
# Any information required to complete the transaction and whether it is to be retained by the verifier. | # 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. | # Any optional information that the verifier wishes that is not required by the immediate transaction. | ||
| − | It is the responsibility of the [[User Agent]] to: | + | * It is the responsibility of the [[User Agent]] to: |
| − | # Display the information to the | + | # Display the information to the holder in a language that the user can understand. |
| − | # | + | # Input the holder's response |
| + | |||
| + | ===Taxonomy=== | ||
| + | * Holder | ||
| + | * Verifier | ||
==Current Standard Request Messages== | ==Current Standard Request Messages== | ||
Revision as of 10:18, 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
- Verifier
Current Standard Request Messages
These are all call Authorization Requests rather than Access Requests, which is the typical current transaction type.
