Les Hazlewood

Per [discussion here](https://github.com/jwtk/jjwt/pull/658#issuecomment-1101614067), this has been addressed in the `jwe` [#178] branch.

I think I understand what you're saying - let me reformulate it to see if we're on the same page: The current exception indicates that the jws specified is an...

Thanks for the clarification!

@hyperxpro this will be in the JJWT 1.0 release.

Java doesn't support `.pem` files natively. You'll need to convert from .pem to a format that Java understands. For example: http://stackoverflow.com/questions/11787571/how-to-read-pem-file-to-get-private-and-public-key

@lekhasy your question is a general JVM question (about key pair files) and not related to JJWT specifically. Did you read my comment above about converting .pem files on the...

Just a follow up: This is currently outside the scope of JJWT since it s a general Java question (of how to convert a .pem file (or contents) to java...

What is the suggested fix in JJWT for this issue? Without a suggestion or PR, it doesn't seem like there is anything to be done?

Is it to change the method signatures from these: ``` java Key resolveSigningKey(JwsHeader header, Claims claims); Key resolveSigningKey(JwsHeader header, String plaintext); ``` to these: ``` java Key resolveSigningKey(JwsHeader header, Claims...

Yes, but to a slightly lesser degree while we're on 0.x. Once we hit 1.0.0, we'll need to be very strict about semantic versioning. That said, I don't think this...