-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement the device authorization endpoint #2
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, mostly style comments..
The WriteAccessError is used to construct error responses as described in Section 5.2 of [RFC6749]. It is not limited to access token responses. Perhaps we should rename the function to Rfc6749TokenError.
cb19a90
to
93b9238
Compare
I added docs to all public functions/packages and tried to fix as much as possible. I didn't make some of the style changes to keep consistency with the project style. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
generally looks ok.. a few remaining comments.. and you might want to change the copyright year to 2024 in all the files you've added.
6322f68
Implement the device authorization endpoint. The changes in this PR are based on the work done in ory#701 (a lot of the work is taken unchanged).
This PR is intended to implement the logic described in paragraphs RFC8628 - Section 3.1 and RFC8628 - Section 3.1.
These changes are tested using a hydra fork.
Even though this PR includes only ~half of the work needed to implement the device flow, it is still quite chunky. Perhaps I should try to break it down further.