-
Notifications
You must be signed in to change notification settings - Fork 409
feat: make both crypto implementations support sign #727
Conversation
…h-library-nodejs into pad-base64-test-crypto
Codecov Report
@@ Coverage Diff @@
## master #727 +/- ##
==========================================
- Coverage 84.69% 84.37% -0.33%
==========================================
Files 18 18
Lines 941 947 +6
Branches 209 209
==========================================
+ Hits 797 799 +2
- Misses 84 88 +4
Partials 60 60
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #727 +/- ##
==========================================
- Coverage 84.69% 84.37% -0.33%
==========================================
Files 18 18
Lines 941 947 +6
Branches 209 209
==========================================
+ Hits 797 799 +2
- Misses 84 88 +4
Partials 60 60
Continue to review full report at Codecov.
|
bcoe
left a comment
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.
rubber stamp approval, looks reasonable to me.
We actually don't really need it for now since the JWT code uses
jws/jwato sign the authentication token, but since I started digging into this, I just decided to make twocryptoimplementations be similar in case if we need it later.