4 ms·
Another benefit is providing a standard way to access multiple services at once with a single token. It is possible to force a logout on the server side if a p
by stephenhuey 10y ago
Another benefit is providing a standard way to access multiple services at once with a single token. It is possible to force a logout on the server side if a problem arises, and you wouldn't need to store these invalidated tokens in the database because it'd likely be a small blacklist you make available to all the servers (and a blacklisted token would be in that list only until the expiration time).
- StevePerkins 10y ago> access multiple services at once with a single token If you're talking about multiple microservices under your own control, then they could all work with your distributed session store just as easily (if not more so). If you're talking about SSO across multiple third-party services, then perhaps JWT could be a nicer solution than SAML. However, here you're talking about a single-digit percentage of edge cases. Not enough to declare "JWT over sessions" as a general rule.