Skip to content

Protocol Flow Diagram #231

@jricher

Description

@jricher

The protocol flow diagram in 1.2 is confusing to readers, and it's not uncommon for a reader to think "Resource Owner" is another computer alongside the Authorization Server and Resource Server. This is further confounded by the text:

The authorization request can be made directly to the resource owner (as shown),

With the removal of the password grant, this should be updated both in the diagram and the text to show that the authorization grant is mediated through the AS. Even better, I would argue that this protocol flow is too abstract to be useful in most explanations, and the diagram does more harm than good.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions