Authentication

Authenticating with Digest and NTLM

Answer a server's Digest or NTLM challenge with a username and password.

Overview

Some servers don't accept credentials up front. Instead, they answer the first request with 401 Unauthorized and a challenge, and the client proves it knows the password in its reply. Digest and NTLM both work this way. Relay answers the challenge for you, so you send the request once and see the final response.

To use either type, open the Auth tab of a request, folder, collection or workspace, click the auth type menu and choose Digest Auth or NTLM.

Authenticate with Digest

Choose Digest Auth and enter a Username and Password.

Relay sends the request without credentials first. When the server responds with 401 and a WWW-Authenticate: Digest challenge, Relay computes the response from your password and the server's challenge and sends the request again. The response you see is the one to that second request.

Relay supports the MD5, MD5-sess, SHA-256 and SHA-256-sess algorithms. When the server offers more than one, Relay uses SHA-256. If the server offers only algorithms Relay doesn't support, the request fails with a message that names them.

If the credentials are wrong, Relay doesn't keep retrying: you see the server's 401. Relay answers a second challenge only when the server says its nonce was stale.

If the request has its own Authorization header in the Headers tab, Relay sends that header and doesn't answer the challenge.

Note

Digest isn't supported for WebSocket requests. A WebSocket request whose auth resolves to Digest shows a notice in its Auth tab and can't connect until you choose another type.

Authenticate with NTLM

Choose NTLM and fill in the form:

  • Username: The account's user name.
  • Password: The account's password.
  • Domain: The Windows domain, if the account needs one. Relay sends the user name as DOMAIN\user.

When the server asks for NTLM, Relay supplies these credentials and macOS performs the NTLM handshake. If the server rejects them, Relay stops and shows the server's 401.

NTLM authenticates the connection rather than each request, so it requires a server that uses HTTP/1.1. Kerberos isn't supported; when a server offers both Negotiate and NTLM, Relay uses NTLM.

See Also