Consent and devices
Docs version v1 (main)Nauthera is pre-1.0, in a design-partner programUpdated
Consent
A request with prompt=consent, or one a client must ask for, shows /consent after the
user is signed in. Everything on it comes from the server's reading of the validated
request, never from the address bar: the application, the account, each permission, the
service the access is limited to, and a warning when the request carries structured details
the screen cannot show. See Sessions, Consent & Logout.




Allow returns a code to the application; Deny returns access_denied. A grant is
remembered, so the same request is not asked again. A request the server can no longer
describe shows no permission list at all, with Sign in to start over:

Connect a device
A device using the device flow (RFC 8628) shows a code and the address /device. The user
opens it, signs in if needed, enters the code, and approves.





A device's own address can fill the code in. The approval names the account, with Switch account, and how long the request has left. Wrong codes are refused one at a time; too many stop the request, and the device has to start again.