Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • 2
    $\begingroup$ FYI, the draft spec says that HMAC SHA-256 MUST be implemented while ECDSA (or RSA) MAY be implemented. Just wanted to point that out. Poncho's answer is spot on. $\endgroup$ Commented Nov 18, 2015 at 19:23
  • $\begingroup$ I think "implemented" is a qualifier for libraries/providers, but "implemented on your website" could mean something closer to configuration, where you may want to use one and only one. Best to be stringent to avoid JWT security holes: mixing symmetric (HMAC) and asymmetric (RSA/ECDSA) algos in your composed auth implementation is bound for disastertown. $\endgroup$ Commented May 26, 2020 at 19:20