Use along KMS asymmetrical key
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- aws, javascript, node.js
- Domain
- backend, documentation, security
Research direction
The issue names jwt.sign with RS256 and AWS KMS Sign/VerifyCommand, but no repository file or test. First determine whether a library change is requested or whether this needs usage guidance; then define the supported KMS flow and a documentation or test target before implementation.
Written by the indexing model from the issue text.
Description
I have a question regarding the use of this library. If I want to use my asymmetrical KMS key (KeySpec: RSA_2048, KeyUsage: SIGN_VERIFY), from my understand, the private key would be used to sign, while the public key would be use to verify/decode. But since the method jwt.sign with algorithm: 'RS256' requires the following a asymmetrical private key, I would have to generate or download the pem file and link it right?
But it defeat the purpose of having asymmetrical key in KMS while using a pem file. So my undertand if that it makes more sense for me to just use kms Verify/SignCommand methods instead of this library () ? Or am I mixing concepts?
Thank you!
- Dominant language
- JavaScript
- Stars
- 18.2k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from auth0/node-jsonwebtoken
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
auth0/node-jsonwebtoken#1042 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
auth0/node-jsonwebtoken#1000 · 2 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 65/100
auth0/node-jsonwebtoken#1046 ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
auth0/node-jsonwebtoken#1034 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
auth0/node-jsonwebtoken#1032 ·
All issues in auth0/node-jsonwebtoken
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mksglu/context-mode#1200 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
neondatabase/website#5944 ·
-
module: core
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
bigbluebutton/bigbluebutton#25849 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jaegertracing/jaeger-ui#4506 ·