I am looking to add a SSL cert to our website, which normally is a simple matter, but we have run into a complication that I am currently unsure how to work around/resolve.
Our server is currently securing a site that is a redirection from another server and we are finding that we cannot bind two certs to the same ip.
Some time ago, our Marketing department wanted our users to be able to log into the application site from our public site (company.com) and retain the url of 'app.company.com'. The public site is created and maintained by another organization, with the entire site already under https.
To facilitate their request, we created a new site, 'app' on the application.com server, installed their cert, and bound it to the 'app' site. This site uses the host name 'app.company.com' and points to the same folder/code as the application.com site.
We now need to secure the application and all access from application.com, but are unsure how to move forward.
So far, we have tried replacing their cert with ours, which does work but brings the 'cert does not match domain' warning on the client, which we need to avoid. We have tried to add our cert to the default site in application.com, but we get the 'binding is also assigned to another sites binding', which prevents the access from the public site.