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
-----BEGIN PUBLIC KEY-----
MIGbMBAGByqGSM49AgEGBSuBBAAjA4GGAAQBxz3Jx59YM4kRV2sG/nzp56XfHQ0a
oYJOsombL1faFCr7u7b/uV2rwrHbWSIhGqgnLY3RqdNShMQ6mAp4dkvQAYsBbLU4
ZHyHCfDZESxzzBBnkJyRXghN4AGODCbHfPYQJ/u8cqt/T1Z6i0d7KT3PAilWMJbs
78jYTXFOkUmSyR41ifM=
-----END PUBLIC KEY-----
But when I try to read the private key, I'm getting this exception: java.security.spec.InvalidKeySpecException: java.security.InvalidKeyException: IOException : version mismatch: (supported: 00, parsed: 01
I tried using the pem files in test directory https://github.com/auth0/java-jwt/tree/master/lib/src/test/resources (ec512-key-private.pem, ec512-key-public.pem) and that pair works. So it might be the way I generate the pem files that's messing things up. If you can share how you generated your test pem files that would be great.
Thx!
The text was updated successfully, but these errors were encountered:
Hi there,
I'm trying to generate ECDSA key pairs, using these 2 commands (on debian):
I end up with these pem contents:
But when I try to read the private key, I'm getting this exception:
java.security.spec.InvalidKeySpecException: java.security.InvalidKeyException: IOException : version mismatch: (supported: 00, parsed: 01
I tried using the pem files in test directory https://github.com/auth0/java-jwt/tree/master/lib/src/test/resources (ec512-key-private.pem, ec512-key-public.pem) and that pair works. So it might be the way I generate the pem files that's messing things up. If you can share how you generated your test pem files that would be great.
Thx!
The text was updated successfully, but these errors were encountered: