ZAP java.lang.IllegalStateException: AuthScheme is null when proxying NTLM authentication

TL;DR

Multiple users hit this on ZAP 2.12 and 2.13 with all add-ons updated. If you see this on 2.13.0 or earlier, upgrade ZAP to a build containing the fix and update all add-ons.

Steps

1. Proxying requests through ZAP to an app that uses NTLM or Windows Authentication blows up with ZAP Error [java.io.IOException]: java.lang.IllegalStateException: AuthScheme is null. Multiple users hit this on ZAP 2.12 and 2.13 with all add-ons updated. It is a real bug in ZAP's HTTP client handling of the NTLM handshake.
2. This was fixed by a ZAP patch and confirmed working by the reporter. If you see this on 2.13.0 or earlier, upgrade ZAP to a build containing the fix and update all add-ons.

When to use

You are seeing this: Proxying requests through ZAP to an app that uses NTLM or Windows Authentication blows up with ZAP Error [java.io.IOException]: java.lang.IllegalStateException: AuthScheme is null. Use this skill when you run into "ZAP java.lang.IllegalStateException: AuthScheme is null when proxying NTLM authentication".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 2.13.0. If you are on something much newer or older, the details may have shifted.

Why this happens

Proxying requests through ZAP to an app that uses NTLM or Windows Authentication blows up with ZAP Error [java.io.IOException]: java.lang.IllegalStateException: AuthScheme is null.

In the thread ZAP java.lang.IllegalStateException: AuthScheme is null when proxying NTLM authentication, the question was: Proxying requests through ZAP to an app that uses NTLM or Windows Authentication blows up with ZAP Error [java.io.IOException]: java.lang.IllegalStateException: AuthScheme is null. Multiple users hit this on ZAP 2.12 and 2.13 with all add-ons updated. It is a real bug in ZAP's HTTP client handling of the NTLM handshake. The verified resolution: This was fixed by a ZAP patch and confirmed working by the reporter. If you see this on 2.13.0 or earlier, upgrade ZAP to a build containing the fix and update all add-ons. Original discussion: https://vectle.com/threads/thr_-fcrq4UYOkO2dqMHBcxnLg