These numbers in the diagram correspond to the numbered steps in the paragraphs below the diagram. Perhaps using non-duplicated numbers would help, such as "1a" and "1b" instead of two instances of "1"? Although I'm not sure how that would work exactly because the "1/2/3" are really just a single action as described by the "Note" below the diagram in your screenshot.
--- Aaron Parecki https://aaronparecki.com https://oauth2simplified.com On Thu, Jul 30, 2020 at 8:43 AM Warren Parad <wpa...@rhosys.ch> wrote: > > https://www.ietf.org/id/draft-ietf-oauth-v2-1-00.html#name-authorization-code-grant > > Can we avoid using (1, 2, 3) on the left side of the diagram to describe, > I'm not even sure what they are supposed to represent, not to mention the > RO in the diagram doesn't really provide value (for me) relevant to the > code grant flow. It's confusing to see these numerical identifiers twice in > the same picture. But maybe there is something hidden in this that I'm > missing, still 3a and 3b could be used to identify different legs of the > same code path. > [image: image.png] > > > *Warren Parad* > Secure your user data and complete your authorization architecture. > Implement Authress <https://bit..ly/37SSO1p>. > <https://rhosys.ch> > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth >
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
