Digest Authentication
HTTP Digest authentication (RFC 7616) is a challenge-response protocol that avoids sending passwords in plaintext. Unlike Basic auth, which base64-encodes credentials, Digest auth hashes the password with a server-provided nonce. This makes it more secure over unencrypted connections.
- Open a request and click the Auth tab.
- Select Digest from the type dropdown.
- Enter your Username and Password.
Nouto handles the two-request handshake automatically when you click Send.
How It Works
Section titled “How It Works”The Digest flow is transparent. You only see the final response:
- Nouto sends the initial request without credentials.
- The server responds with
401 Unauthorizedand aWWW-Authenticate: Digestheader containing a challenge: realm, nonce, qop, and algorithm. - Nouto computes a hash from your username, password, the challenge parameters, and the request method and URI.
- Nouto resends the request with an
Authorization: Digestheader containing the computed hash. - The server validates the hash and returns the actual response.
Supported Algorithms
Section titled “Supported Algorithms”The algorithm is determined by the server’s challenge. Nouto supports:
| Algorithm | Notes |
|---|---|
| MD5 | Default, most widely supported |
| SHA-256 | More secure, defined in RFC 7616 |
| MD5-sess | Session-based MD5 variant |
| SHA-256-sess | Session-based SHA-256 variant |
Supported QOP
Section titled “Supported QOP”| QOP value | Notes |
|---|---|
auth |
Authentication only. Most servers use this. |
| (none) | Legacy mode without QOP, for older servers |
auth-int (body integrity protection) is not currently supported.
Variable Support
Section titled “Variable Support”Both fields accept {{variable}} syntax:
| Field | Example |
|---|---|
| Username | {{DIGEST_USERNAME}} |
| Password | {{DIGEST_PASSWORD}} |
When to Use Digest Auth
Section titled “When to Use Digest Auth”Digest auth is common on:
- Network equipment: routers, IP cameras, NAS devices, and IoT hardware
- Older enterprise web servers and appliances
- Systems that cannot use HTTPS but require more protection than Basic auth
If the server supports HTTPS and a modern auth method, prefer Bearer tokens or OAuth 2.0. Digest auth adds two HTTP round-trips per request, which increases latency compared to stateless methods.
Platform Support
Section titled “Platform Support”| Platform | Digest auth |
|---|---|
| VS Code extension | Supported (MD5, SHA-256) |
| Desktop app | Supported (MD5, SHA-256) |
