-
Notifications
You must be signed in to change notification settings - Fork 153
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
feat: implement RFC 8628 - Device authorization grant #285
Conversation
e3f8197
to
ff05987
Compare
ff05987
to
768a135
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Codecov Report
@@ Coverage Diff @@
## next #285 +/- ##
=======================================
Coverage ? 41.82%
=======================================
Files ? 83
Lines ? 7240
Branches ? 0
=======================================
Hits ? 3028
Misses ? 3913
Partials ? 299 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
reuse the client authentication code for device authorization and introspection.
@livio-a the latest commit includes client authentication for the device endpoint. I've extracted the logic from introspection and made it reusable and tested. TODO as of now:
|
First verify if the client is authenticated. Then the state of the device authorization. If all is good, we take the Client from Storage.
b3b7a99
to
c9ab349
Compare
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.
LGTM and tested with the example implementations
i suggest we change the title to feat: implement RFC 8628 - Device authorization grant
so that ensure to get a new semantic version after the merge
🎉 This PR is included in version 2.0.0-next.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 2.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
closes #264