...
Field | Type | Description |
|---|---|---|
cliendId | long | The id of the client |
code | string | The code for the domain validation for any of the registred redirect uris |
User Interactions
There are three main actors involved in the verification
A. The user that registered a client and needs to submit the verification.
B. The user that reviews the submission
C. The end user using the client
For A (tracked in
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
See that the client is not verified with information about the consequences
Submit a verification if not verified already
Get the domain validation code, with instructions on how to use it. Potentially a file download with the validation code to be placed as is on a web server.
Check the status of the verification, including the domain validation status.
For B the user should be able to:
See the list of submitted verifications
Review the information of the client, including the description submitted with the verification, the client, tos and policy uris and a link to the user profile.
Check the domain validation status for the client, if the domain is not validated yet approval is not allowed.
Approve or reject the verification, allowing to input a reason
For C, the user should be informed if the client is not verified and the consent should be discouraged.
References:
https://tools.ietf.org/html/rfc6749
...