Implementation of Device Code Flow in Vapor OAuth #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
|
Hi, @0xTim and @marius-se, I have taken the initiative to break down the Pull Request for clearer review. Additionally, I have removed all OpenID-related components from the submission. I would appreciate it if you could review these changes at your earliest convenience. Thanks 😄 |
vamsii777
changed the title
|
??? |
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.
In the completion efforts to re-implement the Device Code Flow Integration into Vapor OAuth (PR #27), this pull request marks the finalization of this significant feature. With this submission, I've successfully integrated a full-fledged Device Code Flow into the Vapor OAuth, adhering to the standards specified in RFC 8628.