You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now if ntlmHandler's workstation and domain aren't specified, calls to ntlm.createType1Message (and maybe other methods) fail. They work if workstation and domain are specified, even if they're set to empty strings.
Potentially - I was having issues and changing this fixed it for me. I asked about it in the thread yesterday, we'll see what people say. Regardless, probably makes sense to release this patch and upgrade node-api's dependency because this definitely can cause errors.
Right now if ntlmHandler's workstation and domain aren't specified, calls to ntlm.createType1Message (and maybe other methods) fail. They work if workstation and domain are specified, even if they're set to empty strings.
Discovered this while investigating microsoft/azure-devops-node-api#172
FYI - this is where it fails because it tries to call toUppercase on an undefined object
The text was updated successfully, but these errors were encountered: