[OAuth 2.0] add flow diagrams and improve flow description #28
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We should also cite (and probably enable) the device flow, since it is in fact a standard, and is even recommended for devices without displays: https://tools.ietf.org/html/rfc8628 |
mmccool
reviewed
Jul 13, 2020
| +-----------(F)----- Access WoT --------------------------------+ | ||
| Affordance | ||
| ``` | ||
| Notice that steps (A), (B) and (C) are broken in two parts as they pass threw the User-Agent. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As the title says this PR adds protocol diagrams for each flow. Currently, I only added
code,device, andclientdiagrams. I am planning to add the rest very soon. I also made some minor improvements and pointed to a nice IETF draft about OAuth 2.0 over CoAP. I suggest checking it out before the next call. In particular, I think that section 5.2 can be useful for our discussion.