We're running into a few issues with consuming three different maps from a WMS service. They each have their own username and password, and they are differentiated by path, not host name. So e.g. https://wms.example.com/map/1 with user 'abc' and https://wms.example.com/map/2 with user 'xyz'.
The problem seems to be that MapInfo is associating saved logins by host name only.
So when we open the first layer and enter the login, then the other, it can no longer refresh the first (it instead throws up the login dialog again) because it expects the login for the second layer should work. MapInfo doesn't see a difference between the two for us.
The best option for us would be if we could store the full username + password for a given WMS layer via its full URL.
Update: Detective work led me to Windows Credential Manager in Control Panel, and there I see MapInfo in fact does store a full URL. The only problem is that in our case, for some reason, it stores something like "Microsoft_WinInet_webmap.example.com:443/dpSpatial" for both of the above paths, which I'm pretty sure causes our issue as it can no longer tell the logins apart.
------------------------------
Jonas Nordlund
Software Developer
Norconsult AB
Sweden
------------------------------