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
Hi, given that many JWT issuers support ES256 signature algorithm when signing tokens it would be good if APICAST also could correctly validate JWT signed using ES256.
Even though ES256 is only recommended and not mandatory within RFC7519, a lot of people are still looking to use ES256 rather than RS256 primarily for performance reasons.
The text was updated successfully, but these errors were encountered:
Hi, given that many JWT issuers support ES256 signature algorithm when signing tokens it would be good if APICAST also could correctly validate JWT signed using ES256.
Even though ES256 is only recommended and not mandatory within RFC7519, a lot of people are still looking to use ES256 rather than RS256 primarily for performance reasons.
The text was updated successfully, but these errors were encountered: