-
Notifications
You must be signed in to change notification settings - Fork 925
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(api/rpc): Implement auth middleware on Server
#1402
Conversation
a98a3b6
to
a1582e9
Compare
Codecov Report
@@ Coverage Diff @@
## main #1402 +/- ##
==========================================
- Coverage 55.33% 54.69% -0.65%
==========================================
Files 180 198 +18
Lines 10962 11903 +941
==========================================
+ Hits 6066 6510 +444
- Misses 4296 4756 +460
- Partials 600 637 +37
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
272450b
to
045cf73
Compare
b118c0f
to
1ec02f9
Compare
…re in server and provide secret from node module
1ec02f9
to
afb894d
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.
Glad that jsonrpc does not actually enforce a specific auth dependency. Would also be nice to have some tests here, but I assume they will come in later PRs
Related to #1187
This PR is based on #1313
It implements:
nodebuilder/node
module to both the node module and the rpc server.rpc.Server
that verifies the given token with the server's secretIn a follow-up PR will come the ability to create an rpc client with elevated permissions (this branch restricts client access to read-only API methods).