Daniel DeGroff

If I can find an evening to hack on the branch I started, I may be able to finish it.

Taking a stab at a major version release of this library to make it more extendable, and taking my EdDSA branch and moving it to a new repo to prove...

Thanks for the feedback @Yaytay. If we update the min. required version of Java, I would likely select an LTS, version 11 or 17.

Commits: https://github.com/FusionAuth/fusionauth-jwt/commit/fd761c642f28fb95e384ac2a6e4bcba23ba89d9c https://github.com/FusionAuth/fusionauth-jwt/commit/4465240de20951a59d8374a8f49460ba6343d731 https://github.com/FusionAuth/fusionauth-jwt/commit/ec26cb764127317a139c9a3638a0d4c19ad0a7b8

I can take a look at adding that capability.

Release 3.6.0 w/ validation for x5c. I'll keep this open to still look at adding certificate verification options.

@GokulMahajan20 - it looks like we are expect the key to be PEM encoded. The `x5c` is not PEM encoded, it is just a `base64` encoded version of the key....

Getting closer. I re-worked the branch and use the `java.util.ServiceLoader` which is a bit cleaner than what I was doing prior.

There is some work in progress to make this library more modular so the base can optionally stay on Java 8, and we can add support for various new algorithms...

LTS versions 8, 11, 17, 21. https://www.oracle.com/java/technologies/java-se-support-roadmap.html Probably safe to ditch Java 8 since support is only available through extended or sustaining support from Oracle.