Our DMS (one failover pair) is IP address based, so no hostnames are in place. We use IP addresses only at this moment.
I have configured the https as per user guide with the self signed certificate that lists the VIP IP address (and other IP addresses of that server) in SAN. The CN configured is the primary IP address of the server. First I kept the http binding in place too. With that configured I can properly connect from a WEB client over https. Cube app works well.
Secondly I removed the http binding. The WEB still works OK, but now I can’t connect with cube app.
I noticed that the previously opened cube app (one opened and logged in before http binding removal) is working fine and normally interact with the DMS.
So it seems the cube app uses http in the initial stage (probably downloading actual version). How to change this initial cube communication to https so cube app will work well?
Hi Milos!
Normally the FQDN's are used, but if the certificate holds the (V)IPs of the agents, that should be fine.
Do you only have this issue when connecting to the VIP? Or do you have the same when connecting to the agents themselves?
Did you have a look at DM Docs - Specifying auto-detection information for an inter-DMA HTTPS connection ? It sounds similar to your issue, so it might just be your solution.
Hi Robin,
I’m keeping the http binding for now so the autodetection shouldn’t be impacted. If we’ll disable the http in the future, we will consider this aspect. Thanks.