News for hackers. Stuff that matters.
Re:Ask HN: What's the current sentiment on JWT for stateless... by aaomidi on Friday December 13, 2019 @02:48PM (#21784740)
Authenticating JWT isn't checking the JWT against an external server.
Re:Ask HN: What's the current sentiment on JWT for stateless... by blackflame7000 on Friday December 13, 2019 @03:25PM (#21785074)
How can you validate that it was properly signed without comparing it to the entity's public key?
Re:Ask HN: What's the current sentiment on JWT for stateless... by cstrahan on Friday December 13, 2019 @04:05PM (#21785457)
Why would you need to make a request to another server for this purpose?

Hint: you don’t — but I figure taking the Socratic approach may be more convincing.

Re:Ask HN: What's the current sentiment on JWT for stateless... by rblatz on Friday December 13, 2019 @04:30PM (#21785709)
You could pre share a public key, but a common way is to use the discovery mechanism in OIDC to automatically manage key distribution/rolling.
Re:Ask HN: What's the current sentiment on JWT for stateless... by blackflame on Friday December 13, 2019 @07:46PM (#21787008)
Because else how do you handle key revocation?
Re:Ask HN: What's the current sentiment on JWT for stateless... by aaomidi on Friday December 13, 2019 @11:32PM (#21787826)
Which is the point of the post.

If you need to do revocation you need to call an external server.

If you need to call an external server why do JWT?

Re:Ask HN: What's the current sentiment on JWT for stateless... by blackflame on Saturday December 14, 2019 @04:19PM (#21792329)
Because pinging another server for a few bytes of data and offloading that working memory to the client side is much more efficient than storing the session data in server memory in between requests. Furthermore a single coordinating key server can work in conjunction with many micro-services to simplify architecture, security, and hardware requirements.