Hello,

When some devices use device authorization, the authorized device may have related web content which it wishes to redirect the user to, such as documentation or a web application which integrates with the device they've authorized.

Does it make sense to allow, as an extension to the device flow, the client to specify a redirect URI? This redirect would not be part of an OAuth flow of course (it's not going to include an authorization code). If the application requires authorization it can do its own new flow in that case.

Other possible solutions could be:

• Provide documentation or a link in consent text or client description. Doesn't require any feature changes but probably not a great experience for the user.
• Allow customization of text on the device login successful screen (for example including a link). This would require updates of course, and is maybe an okay but a little clumsy UX. A better solution might be to allow a client-specific template for this screen, which could then implement any number of behaviors, such as a client-side redirect.
• Provide a link from the device that was authorized. Doesn't require any feature changes but also not as good UX.

Curious if any one else believe this is a reasonable use case and solution.

Thank you,
Alec