Hello first of all I want to say that we plan to upgrade to V3.X eventually but I don’t know when this will happen, meanwhile we are planing to continue using the V2.X, Sorry for the long write before hand.
I am facing an issue with our production servers regarding https connections, internally our IIS contains a Self-signed certificate (which was first designed for internal use) and a trusted company signed certificate which is the one being used for external access.
Whenever I connect to the server internally or externally the web page in fact lets me log in with the trusted certificate, but when I display the viewer for annotations, here comes the issue.
For some reason the viewer starts creating a bunch of references to JS files and CSS files that it need internally for using and displaying the viewer but instead of using the hostname it uses the internal IP of the server, which creates an err-invalid certificate or something because it uses the self signed certificate instead of the trusted one.
First of all this is a breach of security because you are showing to the outside world the internal IP address of the server and second we are having the system use an internal self signed certificate instead of the trusted one all because of the IP it is using.
Is there a way to change the URL from IP to hostname to overwrite that behavior?