title: How do CNAMES work with SSL certificates
body: <p>I work with a web application used by several business units in my organization. The application is accessed using a general URL <code>http://app/</code> but some of the units use a business friendly URL e.g. <code>http://bu1/</code>, <code>http://bu2/</code> etc. </p>
  
  <p>The application is soon to be integrated with a portal that requires it to be configured to use SSL and I was advised to request a certificate using a fully qualified domain name so I went with <code>app.company.com</code>. The certificate has been installed on the server and users access it using <code>https://app.company.com/</code>. </p>
  
  <p>However I would also like them to be able to use <code>https://app/</code> or <code>https://bu1/</code> or <code>http://bu1/</code> etc. I'm not clear on how to do this, I think I have the following options:</p>
  
  <ol>
  <li>Should I have requested a certificate without using the fully qualified domain name, just the CNAME?</li>
  <li>I keep coming across subject alternative names but they appear to relate to different domains and I'd rather the users didn't need to use a domain at all. 3. Shoud I be looking for a wildcard certificate instead? I think one of the posts on here says they are not recommended.</li>
  <li>Do I need a certificate per domain?</li>
  </ol>
  
  <p>Many thanks for any advice!</p>