HMACs and MACs are authentication codes and are often the backbone of JWT authentication systems. Let’s take a look at how they work.

MAC – Message Authentication Code

MACs are exactly what they sound like; small codes that allow receivers of messages to know who the sender was (authentication). A MAC code is calculated by using a message and a secret key as inputs. Anyone who has a copy of that secret key can then verify that that code and message were created by someone with the same key.

One way this is accomplished is by using a hash function, for instance, SHA-256. Simply put, a hash function takes an input and then returns an output, where:

The output is very unlikely to be the same for different inputs

The output is always the same for the same inputs

The output is not predictable – changing the input even slightly results in a seemingly random and large change to the output

Given this, a naive example of MAC generation by the sender could be:

message = 'my message here' macCode = sha256('thisIsASecretKey1234' + message) // send macCode and message

Then the verification by the receiver would be:

// receive macCode and message if (macCode == sha256('thisIsASecretKey1234' + message)){ // verified! }

Note that MACs don’t necessarily need to use a hash function, but a hash can be used as the “signing” mechanism.

An HMAC is a kind of MAC. All HMACs are MACs but not all MACs are HMACs. The main difference is that an HMAC uses two rounds of hashing instead of one (or none). Each round of hashing uses a section of the secret key. As a naive example:

sha256('thisIsASe' + sha256('cretKey1234' + 'my message here'))

Which is a simplified version of the function given in RFC-2104.

Why use HMAC? Why do we need to hash twice?

With many hash functions, it is possible to change the message (without knowing the key) and obtain another valid MAC. We call this a length extension attack. No known extension attacks are known against the current HMAC specification.

HMACs with JWTs

jwt.io

If you’ve ever implemented JWTs for authentication schemes within a web app, then you know that JWTs are wonderful for keeping track of who is who. A JWT (when using HMAC as the signing scheme) is basically just an HMAC message where the message data is a JSON object.

The interesting thing about the JWT system is that the sender and the receiver of the JWT are typically the same entity, that is, the webserver. Look at the following example:

User gives the server an username and password

Server verifies the username and password are correct

Server generates a JWT using HMAC:

hmacCode = sha256('thisIsASe' + sha256('cretKey1234' + '{"email":"lane@qvault.io"}'))

The server responds with the following (decoded) JWT:

header.{"email":"lane@qvault.io"}.hmacCode

User decides to update his/her profile picture by sending the following request:

PUT /users/profile_picture Authentication: Bearer header.{"email":"lane@qvault.io"}.hmacCode {"new_picture": "http://linktopicture.com/mypic"}

The server parses the JWT. The JWT says the user is “lane@qvault.io”

The server verifies that the user really is Lane by validating the HMAC code. Only someone with access to the secret key ‘thisIsASecretKey1234’ could have made the HMAC code that corresponds to the ‘lane@qvault.io’ message

If verification is successful, then the server updates Lane’s profile picture

If you feel that I missed anything important, or have any questions, feel free to contact me!

Thanks For Reading! Follow us on Twitter @q_vault if you have any questions or comments Take some coding courses on our new platform Subscribe to our Newsletter for more programming articles

Related Articles