You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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!
The text was updated successfully, but these errors were encountered: