Web Server certificate question

Bruno Del Sol bruno.delsol at bydesign.fr
Tue Mar 24 10:57:31 EDT 2015

Hi Jim,

Server certificates are bound to a single dns name. Thus, ip adresses, localhost or any nickname you might use to call 
your server wil get you the same warning.


By Design
Bruno Del Sol
bruno.delsol at bydesign.fr
tel (33) 01 48 78 47 37
46, rue de La Tour d'Auvergne
75009 Paris (France)

Le 24/03/15 15:50, Jim Pistrang a écrit :
> Hi all,
> This isn't exactly an Omnis question, but it is related.  Hope someone can help.
> I have an Omnis Javascript application running on a client site.  The app is running on a Mac OS X Server inside their firewall.  The app can be run from outside their firewall via a secure port in their firewall.  When I do this, the url looks like this:
>    <https://12.345.67.89:5922/rfMyApp.htm>
> In the above example, 12.345.67.89 is the IP address of the firewall, and port 5922 is a secure port opened to the server.  Apache is listening on this port.
> This all works perfectly well, except that users get a warning saying that the site may not be secure.  My client has asked that I purchase a trusted certificate for the site.  I have done the following:
> 1) Gave the server a host name of jimsdomain.com
> 2) Registered jimsdomain.com and purchased a trusted certificate.  [note: the domain name is not associated with an IP address]
> 3) Added the certificate in Server Manager on the server, and it shows up as valid
> BUT - I still get warning messages in my browser when I access the app, since the url that I type in <https://12.345.67.89:5922/rfMyApp.htm> does not match the certificate name 'jimsdomain.com'
> Is there a way to do this?  Do I need to install a certificate on the firewall?
> Jim

More information about the omnisdev-en mailing list