This article is going to show you how to invalidate JWTs using the token blacklist method. The token blacklist method is used when creating a logout system. This is one of the ways of invalidating JWTs on logout request.
One of the main properties of JWT is that it's stateless and is stored on the client and not in the Database. You don't have to query the database to validate the token. For as long as the signature is correct and the token hasn't expired, it would allow the user to access the restricted resource. This is most efficient when you wish to reduce the load on the database. The downside, however, is that it makes invalidating the existing, non-expired token difficult.
Why blacklist?
One reason you would need to invalidate a token is when you're creating a logout system, and JWT is used as your authentication method. Creating a blacklist is one of the various ways to invalidate a token. The logic behind it is straight forward and easy to understand and implement.
A JWT can still be valid even after it has been deleted from the client, depending on the expiration date of the token. So, invalidating it makes sure it's not being used again for authentication purposes.
If the lifetime of the token is short, it might not be an issue. All the same, you can still create a blacklist if you wish.
Creating a blacklist
- When your web-server receives a logout request, take the token and store it in an in-memory database, like Redis. We are using this because of speed and efficiency, as you don't want to hit your main database every time someone wants to logout. Also, you don't have to store a bunch of invalidated tokens in your database. Take a look at my approach below;
First, create a middleware to verify the token:
const verifyToken = (request, response, next) => {
// Take the token from the Authorization header
const token = request.header('Authorization').replace('Bearer ', '');
if (!token) {
response.status(403).send({
message: 'No token provided!',
});
}
// Verify the token
jwt.verify(token, config.secret, (error, decoded) => {
if (error) {
return response.status(401).send({
status: 'error',
message: error.message,
});
}
// Append the parameters to the request object
request.userId = decoded.id;
request.tokenExp = decoded.exp;
request.token = token;
next();
});
};
Then,
// This is a NodeJs example. The logic can be replicated in any language or framework.
// 1. The server recieves a logout request
// 2. The verifyToken middleware checks and makes sure the token in the request object is valid
router.post('/logout', verifyToken, (request, response) => {
// 3. take out the userId and toekn from the request
const { userId, token } = request;
// 4. use the get method provided by redis to check with the userId to see if the user exists in the blacklist
redisClient.get(userId, (error, data) => {
if (error) {
response.send({ error });
}
// 5. if the user is on the blacklist, add the new token
// from the request object to the list of
// token under this user that has been invalidated.
/*
The blacklist is saved in the format => "userId": [token1, token2,...]
redis doesn't accept obejcts, so you'd have to stringify it before adding
*/
if (data !== null) {
const parsedData = JSON.parse(data);
parsedData[userId].push(token);
redisClient.setex(userId, 3600, JSON.stringify(parsedData));
return response.send({
status: 'success',
message: 'Logout successful',
});
}
// 6. if the user isn't on the blacklist yet, add the user the token
// and on subsequent requests to the logout route the user
// will be found and the token will be appended to the already existing list.
const blacklistData = {
[userId]: [token],
};
redisClient.setex(userId, 3600, JSON.stringify(blacklistData));
return response.send({
status: 'success',
message: 'Logout successful',
});
});
});
- Then, for every request that requires that the user is authenticated, you would check the in-memory database to check if the token has been invalidated or not. Then, send a response based on the result from the check. Take a look at my approach below;
module.exports = (request, response, next) => {
// 1. take out the userId and toekn from the request
const { userId, token } = request;
// 2. Check redis if the user exists
redisClient.get(userId, (error, data) => {
if (error) {
return response.status(400).send({ error });
}
// 3. if so, check if the token provided in the request has been blacklisted. If so, redirect or send a response else move on with the request.
if (data !== null) {
const parsedData = JSON.parse(data);
if (parsedData[userId].includes(token)) {
return response.send({
message: 'You have to login!',
});
}
return next();
}
});
};
To make the search more efficient, you could remove tokens from the blacklist which have already expired. To do this, we would follow the series of steps below:
- verify the authenticity of the token
- If successfully verified, append the userId, the token itself and its expiration date to the request object.
- Store the token in Redis with the expiration date of the token itself.
// 1. The server receives a logout request
// 2. The verifyToken middleware checks
// and makes sure the token in the request
// object is valid and it appends it to the request object,
// as well as the token expiration date
router.post('/logout', verifyToken, (request, response) => {
// 3. take out the userId, token and tokenExp from the request
const { userId, token, tokenExp } = request;
/**
4. use the set method provided by Redis to insert the token
Note: the format being used is to combine 'blacklist_' as a prefix to the token and use it as the key and a boolean, true, as the value. We also set the expiration time for the key in Redis to the same expiration time of the token itself as stated above
**/
redisClient.setex(`blacklist_${token}`, tokenExp, true);
// return the response
return response.send({
status: 'success',
message: 'Logout successful',
});
});
Then, for every request that requires that the user is authenticated, you would need to check your in-memory database to see if the token has been invalidated or not and then send a response based on the result from the check. Take a look at my approach below.
module.exports = (request, response, next) => {
// 1. take out the token from the request
const { token } = request;
// 2. Check Redis if the token exists. If so, redirect or send a response else move on with the request.
redisClient.get(`blacklist_${token}`, (error, data) => {
if (error) {
return response.status(400).send({ error });
}
if (data !== null) {
return response.send({
message: 'You have to login!',
});
}
// 3. If not, move on with the request.
return next();
});
};
Conclusion
This is one of the various ways to invalidate a token. I personally use this approach and it works efficiently. I would like to know your thoughts in the comments.
Thank you for reading, cheers.
Top comments (25)
If you are using JWT, you want your authorization system to be stateless, right? š. When you introduce blacklisting, you make your authorization stateful! What sense does it make?
This ends up maintaining the list of "logged out", so why not maintain the list of "logged in" and DO NOT use a self-contained token (that exposes the content to anyone), but an opaque token (like session-id) and manage the session on the server. Server-side sessions are by design more secure and logging out isn't any problem.
TL; DR: Blacklisting stateful tokens does not make sense (despite the hype around JWT and cool blacklisting "technique", which probably is fun in developing š¤·āāļø).
Good question - from work I did designing a JWT based authorisation system, we concluded that a store of invalidated but within expiry tokens would be several orders of magnitude smaller than a list of valid, in use tokens, so this significantly reduces the work/load/networking required to provide token safety through a stateful revocation mechanism.
In our case we were happy to accept the risk of a transient session token being used at any point within it's issued lifetime (an order of minutes), but wanted to revoke long-term tokens used for API keys (lifetime of months) within a similar order of minutes. We chose to publish revoked token identifiers (via their unique
jtifield) internally to consuming services at the same time as we published the JWT signing keys, by extending the OpenID connect metadata documents that all services regularly collect (order of minutes) from our source of truth / authentication database. Auth0 blogged a similar approach a number of years ago that was our inspiration: auth0.com/blog/denylist-json-web-t...Hi there! So you were maintaining a "small" list of invalidated tokens that still hadn't expired? If yes, did this approach include periodical scanning for expired tokens? Was this really advantageous compared to regular sessions with opaque tokens?
Yes, the list was 10s of token IDs, owned and updated (hourly IIRC) by an authentication service, and critically, published as a static JSON file to a global CDN. Advantages are: zero coupling between global systems and authentication service (unlike opaque tokens that require a much more coupled global store); very little coupling between the many autonomous global development teams consuming this information in their own services (this was important for our 1000+ people, multi-company global org!).
Interesting! What if these global development teams didn't check against this JSON file? Just thinking aloud about the practical perspective. Was there any mandate on this?
There was a mandate, as part of the global common user management function (which included a set of acceptance tests that had to pass).
Interesting case. So this was implemented for long-lived API tokens (order of months)? This must have been a very detailed design process for such an architecture, haven't been?
I believe you had scalability challenges to tackle! Just curious: standard OAuth with rotating refresh tokens was not feasible?
Was the ratio between active long-lived API tokens (many) and invalidated ones (few) one of the deciding factors?
Yes, we looked at the risk of accepting tokens over different timescales, and concluded that only API keys were a material risk to us (use outside of contract, reputation loss), most of the risk of shorter term token misuse was carried by our customers as it would be their account that got billed if they leaked a token. I should note that the majority of our customers (80%+) used our API integration, not the browser-based UI (for which we had standard OAuth with rotating session tokens and refresh tokens with lifetimes on the order of a few days).
At the time I retired, we were handling ~1billion API calls a day globally.
Great use case! What a scale!
Amazing, would definitely look into. Thank you!
Thank you for your feedback. You have a point, I use sessions also and it works as you've said. There are many ways to go about things, that's how code works, there isn't one way to it. I'm just sharing my knowledge, I didn't say this is the best way or most secure to go about it. Sessions have their flaws as do JWTs, it's just another way. You have your opinion and I'm happy you shared it. Thank you again.
What are the flaws of sessions (in comparison to this "JWT blacklisting")? I am not sure I understand your point.
Great article :) JWT is an awesome topic.
Protip: you can use pub/sub model of Redis to notify the app about new tokens. However, the main JWT has to be stateless like you mention and possible to verify without additional calls so a better approach is to blacklist refresh tokens and make general token live very short.
True, this is another way to go about it. Thank you for the feedback
I think it is not a good idea to add a JWT token to a denylist as it is encoded in base64... You can add "==" to the end of your token to bypass the denylist check and login.
That's if the user somehow gets access to the token and sends it with a request, which is very hard expect they're some hacker or something. And adding extra characters to the end of the token will make sure it's invalid and the verify token middleware checks for that.
If I didn't get you right, please explain.
The token is in the header "Authorization" right ? Any user can update the Authorization token in the request. Maybe it's not easy for everyone but it is possible.
JWT is encoded in base64, but in base64 you can add padding with "=" without changing the encoded message. "Hi dev.to !" in base64 is "SGkgZGV2LnRvICE=" but also "SGkgZGV2LnRvICE==" or "SGkgZGV2LnRvICE===".
So if you check the encoded token in the denylist you can just add "=" at the end of the token to bypass the denylist and use the token without changing the decoded value.
Here is the RFC for the base64: tools.ietf.org/html/rfc4648
Oh wow, didn't realize this. Thank you for sharing. Will check it out.
This is why our design revoked tokens via their
jtifield, which is not changeable provided the tokens are correctly signed (with an RSA or elliptic curve key pair). it does require all tokens to be parsed, but we can delegate that to a trusted library that should be resistant to attack...But then we need to scan the redis store at some intervals to ensure removal of expired tokens.
You could If you want to, but it would be redundant as the expiry date works automatically to ensure it is removed at the set date. Since the expiry date is the same as the one on the token itself, I don't think there is need to check at intervals anymore
Yes, correct. But, my point is the expired tokens would pile up eventually consuming a significant part of the store memory at some point of time.
True, thank you for the feedback.
Maybe choose a shared/distributed store that supports automated expiry of records (eg: MongoDB, Zookeeper, etc.), or can execute scheduled jobs (yes, SQLserver could be the right answer :))
Thank you for this, I appreciate it!