Authorization
Digest Auth
Answer a Digest challenge from the server without sending the password, with the steps Luvin follows and a verified example.
Use Digest Auth when the server answers 401 with a WWW-Authenticate: Digest header. Digest never sends the password: it sends a hash computed from it.
Example
Section titled “Example”Request GET https://httpbin.org/digest-auth/auth/user/passwd.
Type Digest Auth, Username user, Password passwd. The final response is 200:
{ "authenticated": true, "user": "user", "authorized": true}Without credentials the same request answers 401.
What Luvin does
Section titled “What Luvin does”- Luvin sends the request without credentials.
- The server answers
401withWWW-Authenticate: Digestand a realm and a nonce. - Luvin computes the answer and sends the request again with
Authorization: Digest …. - You see the second response. The time shown adds both calls.
If the first answer is not a 401 with a Digest challenge, Luvin does not repeat the request.
Fields
Section titled “Fields”| Field | What to write |
|---|---|
| Username | The user. |
| Password | The password. A secret field. |
Details
Section titled “Details”The second request carries username, realm, nonce, uri, qop, nc, cnonce, response and, when the server gave them, opaque and algorithm.
- The algorithm is MD5 unless the server asks for SHA-256. The
-sessvariants are supported. - When the server offers several
qopoptions, Luvin prefersauth, thenauth-int. - Works in requests, in the collection and in a workflow.
Secrets
Section titled “Secrets”Password is a secret: stored encrypted on your computer when typed as-is. Username goes to the file. See Secrets.