Content · Programming · Python

Python HMAC Authentication with hmac.new()

HMAC authenticates a message using a shared secret key and hash algorithm. It can detect modification when the key is known only to trusted parties.

2 views Published Oct 18, 2026 Updated Oct 18, 2026 Admin

HMAC authenticates a message using a shared secret key and hash algorithm. It can detect modification when the key is known only to trusted parties.

What You Will Learn


This lesson focuses on HMAC Authentication with hmac.new(). You will connect the operation to a concrete input, inspect the result and identify the situation in which a different approach would be safer or clearer.

Security-sensitive operations are correct only when they remain safe under invalid, unexpected and attacker-controlled inputs. A normal-case example alone does not establish that safety.

How It Works


Decide which inputs are trusted, which privileges are needed, how secrets are managed, and how the result is validated. Security primitives solve specific problems; using the wrong primitive can create a false sense of protection.

Check whether the function returns bytes or text, which security property it provides, and where its output will be stored. These examples use demonstration data; never reuse test keys, salts or tokens as production secrets.

Worked Example


The following example isolates the main behavior so you can run it from a local Python installation. Read the inputs first, then follow the operation and the final printed result.

import hmac, hashlib
key = b"test-secret-not-for-production"
message = b"order=17"
tag = hmac.new(key, message, hashlib.sha256).digest()
print(hmac.compare_digest(tag, hmac.new(key, message, "sha256").digest()))

Understanding the Example


Start with the setup and import statements; these define the objects that the operation needs. Follow each assignment or function call in order, noting which arguments are provided and whether the operation creates a new value, changes existing state or returns a result. Finally, inspect the printed value or assertion rather than assuming that the operation worked.

The important behavior demonstrated here is: HMAC authenticates a message using a shared secret key and hash algorithm. It can detect modification when the key is known only to trusted parties. The example uses deliberately small values so the intermediate result is easy to reason about. A larger application must still handle validation, errors and resource cleanup.

Example Output


True

This output was obtained by running the local example in the available Python environment. Verify that the values match your reasoning, then change one input and try again.

When to Use This Approach


Use small local demonstrations to learn each primitive, and adopt current security parameters and reviews before handling real secrets or sensitive data.

Important Behavior and Edge Cases


Constructing a custom MAC by concatenating a secret with a plain hash instead of using HMAC.

Prefer proven libraries and narrow APIs over custom cryptography, string-based command construction or broad exception suppression. Do not print credentials, generated tokens or confidential payloads in logs.

Practice Exercise


Modify the message and verify the computed tag no longer matches.

Before running your modified code, predict the output or expected failure. Confirm the result using at least one ordinary case and one invalid, missing or boundary input. If the operation accesses external resources, first exercise it against a controlled local or test environment.

Common Beginner Mistakes


  • Constructing a custom MAC by concatenating a secret with a plain hash instead of using HMAC.
  • Prefer proven libraries and narrow APIs over custom cryptography, string-based command construction or broad exception suppression. Do not print credentials, generated tokens or confidential payloads in logs.

Key Takeaways


  • HMAC authenticates a message using a shared secret key and hash algorithm. It can detect modification when the key is known only to trusted parties.
  • Choose this technique for the problem it solves, but validate inputs and follow the cleanup and failure behavior shown above.
  • Next practice step: Modify the message and verify the computed tag no longer matches.
Share this resourceSend this page to someone who may find it useful.