Skip to content

Windows-integrated auth (Negotiate/NTLM) and Digest — the .NET tool cannot call .NET intranet APIs #679

Closed

Description

@thomas-stegemann

Why

The auth surface is broad — Bearer, Basic, API key, signed JWT, OAuth 2.0 (client credentials and authorization code + PKCE), custom token endpoint, AWS SigV4, mTLS, cookie jar. Windows-integrated auth is missing.

For the tool that positions itself as the .NET workbench, this is the most awkward single gap in the product: intranet APIs behind Windows auth are precisely our audience, and we are the one tool in the field that cannot call them. Yaak supports NTLM; the JetBrains HTTP Client supports Digest and Negotiate.

Digest is missing too — httpyac and Rider both have it, and it still shows up on older internal services and on network equipment.

What

  • Negotiate / Kerberos — the default path on a domain-joined machine, using the ambient credentials (UseDefaultCredentials semantics) with an explicit opt-in, never silently.
  • NTLM — explicit credentials (domain, user, password) as a fallback where Kerberos is unavailable.
  • Digest — RFC 7616, including the qop variants that actually appear in the wild.
  • Credentials come from the existing secret handling (keyring / {{secret.*}}), never stored in plain text in a workspace file.
  • Available on the same auth-configuration surface as the existing types, and applied consistently across REST, SOAP, OData and any other protocol going over HTTP.
  • Reachable from the CLI and MCP as well as the workbench, per the parity rule.
  • Where a scheme cannot work (non-Windows host for integrated auth, protocols that do not go over HTTP), the UI must say so and hide the option rather than offering something that will fail — capabilities are queryable, and a thin source reports what it cannot do.

Acceptance criteria

  • A request against an IIS endpoint requiring Negotiate succeeds from a domain-joined Windows machine without typing a password.
  • NTLM with explicit credentials succeeds where Negotiate is unavailable.
  • Digest succeeds against a server offering auth and auth-int.
  • Credentials never appear in an exported collection, a recording, a report, or a code-export snippet.
  • On a platform where integrated auth is unavailable, the option is not offered and the reason is stated.

Activity

  1. thomas-stegemann commented on Sep 30, 2026

    @thomas-stegemann
    MemberAuthor

    Erledigt in d247cb2 (ausgeliefert mit 2.9).

    • Windows (Negotiate/Kerberos→NTLM) mit angemeldetem Konto, nur auf Windows angeboten (/api/auth/capabilities nennt sonst den Grund).
    • NTLM mit Domäne/Benutzer/Passwort, nur NTLM/Negotiate-Challenges angeboten.
    • Digest nach RFC 7616 (MD5/SHA-256, -sess, qop auth + auth-int, userhash, stale-Retry) in eigener Implementierung.
    • Für REST, SOAP, OData, GraphQL, SSE, JSON-RPC, MCP und die SignalR-/WebSocket-Handshakes; ein Handler je Identität, damit NTLM-Verbindungen nie gemischt werden.
    • CLI bowire call --negotiate | --ntlm | --digest; MCP über den Marker in bowire.invoke.
    • Nebenbei: SOAP und OData schickten gar keine Metadata-Header (auch kein Basic/Bearer) – behoben.
    • Tests: RFC-7616-Testvektoren, Digest live gegen einen Server, der jedes Feld prüft.
      Nicht automatisiert getestet: Negotiate gegen einen echten IIS in einer Domäne – dafür braucht es eine domänenverbundene Maschine; bitte einmal von Hand prüfen.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Projects

  • Status
    Done

Relationships

None yet

Development

No branches or pull requests

Issue actions