This topic contains 1 voice and has 0 replies.

  • Author
    Posts
  • #25659
     chiragshah501 
    Participant

    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.”

    Thanks.

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

©2019 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?