Different authentication behavior when switching my URL path from "ServerAPI" to the newer "ManagementServer"

It comes down to the fact that the authentication techniques I’m being presented with change depending on whether I use https://[hostname]/ServerAPI/ServerCommandService.asmx or https://[hostname]/ManagementServer/ServerCommandService.asmx to do a login.

The header of the response to my posting a login request is:

HTTP/1.1 401 Unauthorized
Content-Type: text/html
Server: Microsoft-IIS/10.0
WWW-Authenticate: Negotiate
WWW-Authenticate: NTLM  <---- Missing for ManagementServer
X-Powered-By: ASP.NET
X-Frame-Options: SAMEORIGIN
Date: Sat, 22 May 2021 11:21:47 GMT
Content-Length: 1293

When using the URL with the path that contains “ManagementServer” I don’t get the option for NTLM and it fails when I then go on to attempt to authenticate with it.

I’m not sure how a misconfiguration could affect one endpoint and not the other.

Any help would be appreciated.

Thanks

Jim

I believe the changes to be expected.

Please see -

https://doc.developer.milestonesys.com/html/index.html?base=gettingstarted/intro_soap_protocols.html&tree=tree_3.html