add support for ES algorithms

[swaeberle]

See #117

[JoshMcCullough]

Thanks for this. Can you please add tests matching those for RS*?

[swaeberle]

Thanks for this. Can you please add tests matching those for RS*?

I'll have a look on this, too!

[JoshMcCullough]

Sorry for the delay. It's close -- make sure all instances of ES 512 are 512 and not 521.

[swaeberle]

Sorry for the delay. It's close -- make sure all instances of ES 512 are 512 and not 521.

In fact the naming is no mixup but intended.

I used the elliptic curve NIST P-521 to create the keys with -521 suffix. Only later the key is used in combination with SHA-512 to form JWT algorithm ES512 (as defined by RFC 7518 section 3.4).

So the number originates from the named elliptic curve, not the hash function.

Though for the other JWT algorithms, named curve and hash function are equivalent.

[beeing]

Hi, any resolution on this? I'm interested to use it with this too. Thanks in advance!

[swaeberle]

@JoshMcCullough Are you fine with keeping the test keys' file names or do you insist in renaming them?

[JoshMcCullough]

@JoshMcCullough Are you fine with keeping the test keys' file names or do you insist in renaming them?

Thank you for clarifying -- my mistake.

[JoshMcCullough]

v2.1.0: https://github.com/TeslaGov/ngx-http-auth-jwt-module/releases/tag/2.1.0