# Help with NTLM Authentication and POST commands in 8.3

**URL:** <https://forum.inductiveautomation.com/t/help-with-ntlm-authentication-and-post-commands-in-8-3/112465>\
**Category:** Ignition\
**Tags:** ignition83, scripting\
**Created:** [November 26, 2025, 8:49pm UTC](https://forum.inductiveautomation.com/t/help-with-ntlm-authentication-and-post-commands-in-8-3/112465 "2025-11-26T20:49:20Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Lynn\_Martineau](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@Lynn\_Martineau](https://forum.inductiveautomation.com/u/Lynn_Martineau)\
**Post date:** [December 4, 2025, 2:23pm UTC](https://forum.inductiveautomation.com/t/help-with-ntlm-authentication-and-post-commands-in-8-3/112465/6 "2025-12-04T14:23:32Z")

</div>

Our IT department said wireshark is not justified for this issue.

The DEV team that wrote the APIs I’m trying to call said that NTLM is the only authentication method they will support and,

> [@Calling Web API using windows(NTLM) authentication](https://forum.inductiveautomation.com/t/calling-web-api-using-windows-ntlm-authentication/90365/2):
>
> There's no support for NTLM authentication in either the old `system.net` functions or the newer `system.net.httpClient` functions. You won't be able to call this API if that's the only authentication mechanism supported.

I think I’ll have to ask the customer (internal) to drop this requirement 😩

---

_[View the full topic](https://forum.inductiveautomation.com/t/help-with-ntlm-authentication-and-post-commands-in-8-3/112465)._