title: SSL wildcard certificate - multiple subdomains and multiple tiers
body: <p>I have the following requirement to map many domains to a single site instance for my web application, and I'm wondering if this is solvable using a single SSL wildcard certificate in IIS 7, or whether I need two wildcard cerfiticates.  Here's my current plan: </p>
  
  <pre><code>Certificate #1 - *.mydomain.com
  https://customer1.mydomain.com
  https://customer2.mydomain.com
  https://customer2.mydomain.com
  etc...
  
  Certificate #2 - admin.*.mydomain.com
  https://admin.customer1.mydomain.com
  https://admin.customer2.mydomain.com
  https://admin.customer3.mydomain.com
  etc...
  </code></pre>
  
  <p>My intentions are the following:</p>
  
  <ol>
  <li><p>A single IP address that all of the above domains map to.</p></li>
  <li><p>Can this be accomplished without the second certificate? I was told that I must have two by both Thawte and Godaddy.</p></li>
  <li><p>The website is really the same site instance for all clients, but a different color scheme and logos will be displayed based on the URL. (hence multiple domain names)</p></li>
  <li><p>I do not want to have to replace the certificate each time I add a new customer, hence the wildcard certificate.  </p></li>
  <li><p>I want to automatically redirect any request that comes in as http:// or blank to any of the above URLs to its https:// counterpart.  For example, <a href="http://customer1.mydomain.com" rel="nofollow">http://customer1.mydomain.com</a> would automatically redirect the user to <a href="https://customer1.mydomain.com" rel="nofollow">https://customer1.mydomain.com</a>.  I am currently doing this with a regular certificate, but since we're growing, I want to switch to wildcard.  Is this still possible with the URL Rewrite IIS Snap-In?</p></li>
  </ol>
  
  <p>I'm curious if anything I'm doing here is bad practice or if there is a better approach.</p>
  
  <p>Thanks</p>