Hi. I found that crv claim could be wrong when I use secp256k1.
This PR fixes a crv claim to follow the standards so that I can use secp256k1 and parse resulting JWTs with other libraries.
the problem is that crv claim is secp256k1. It is an OpenSSL style curve name so it should be P-256K according to this. Also, ruby-jwt assumes crv claim to be P-256K. Because of that, I can't decode JWT created using json-jwt.
Hi. I found that crv claim could be wrong when I use secp256k1. This PR fixes a crv claim to follow the standards so that I can use secp256k1 and parse resulting JWTs with other libraries.
the problem is that crv claim is
secp256k1
. It is an OpenSSL style curve name so it should beP-256K
according to this. Also, ruby-jwt assumes crv claim to beP-256K
. Because of that, I can't decode JWT created usingjson-jwt
.