As we know, the Device Flow in AM is designed for client devices that have limited user interfaces, such as a set-top box, streaming radio, or a server process running on a headless operating system.
I totally understand the handshake between the primary client device & AM as well as another rich device (laptop) & AM
with the help of device-code and user-code respectively.
Basically it is straight forward i.e., Granting Consent with a User Code Using a Browser in the Device Flow
However, the doc. also has another flavor i.e., Granting Consent with a User Code Without Using a Browser in the Device Flow.
I am not at all following how it is possible. The doc says that client makes a POST call to the authorization server’s authorization device user endpoint specifying in a cookie SSO token of the user. I do not understand how the client devices that have limited user interfaces get the SSO cookie of the user.
Would you please explain this flow which they call it “Granting Consent with a User Code Without Using a Browser in the Device Flow.”