I have a web application that is utilizing the wildcard certificate for a specified IP address (at port # 443) in the Production server (has IIS 7). Now, I want to utilize the same wild card certificate, IP address & port # for another web application on the same server. However, the host header text box is disabled when I try to edit binding.
Based on my findings so far and going thru few blogs, I can (either use appcmd utility to change the binding or) rename the SSL certificate's friendly name, which would enable the host header text box. Hence, I would be able to use the same wildcard certificate - IP address - Port # combination with different host header for my new web application. I tried this on my laptop and found that it successfully works. However, it renames the wild card for the site that was already using it. I did not observe any negative impact such as the existing site going down or the IIS reset occurring during this process. But, I'm not in favor of trying this out in the production environment, without fully understanding the impact of this change.
In other words, I'm trying to find if renaming the wild card certificate would bring down the sites that are already using it (even if it is momentary) or cause any other undesirable effect? Any help or pointers on this?
