- Generated by
1.8.18
|
Authlete
|
Request to Authlete's /api/device/verification API. The API is used to get information associated with a user code.
More...
Properties | |
| string | UserCode [get, set] |
| The user code input by the end-user. More... | |
Request to Authlete's /api/device/verification API. The API is used to get information associated with a user code.
A response from the device authorization endpoint of the authorization server is JSON which contains a device code, a user code, a verification URI and other parameters. The definition of the response is described in Section 3.2 of RFC 8628 OAuth 2.0 Device Authorization Grant.
After receiving a response from the device authorization endpoint of the authorization server, the client application shows the end-user the user code and the verification URI which are included in the device authorization response. Then, the end-user will access the verification URI using a web browser on another device (typically, s smart phone). In normal implementations, the verification endpoint will return an HTML page with an input form where the end-user inputs a user code. The authorization server will receive a user code from the form.
After receiving a user code, the authorization server should call Authlete's /api/device/verification API with the user code. The API will return information associated with the user code such as client information and requested scopes. Using the information, the authorization server should generate an HTML page that confirms the end-user's consent and send the page back to the web browser.
Since version 1.5.0.
|
getset |
The user code input by the end-user.
1.8.18