title: Third-Party Signed SSL Certificate for localhost or 127.0.0.1?
body: <p>Without divulging TOO much information, I need to setup a web server system that is intended to be used by end users all over the internet. </p>
  
  <p>the use case is such that:</p>
  
  <ul>
  <li>end users are (usually) in their homes behind their local firewalls when connecting to the system. </li>
  <li>The system consists of a remote server hosted by us, strictly over https (using SSL)</li>
  <li>The authorization mechanism requires user account self-creation on the remote server which, upon successful account creation, will then require a piece of software to be downloaded and installed to the end users' computer. This software contains, among other things, a local webserver. </li>
  <li>This "local" webserver must also only allow https connections to the user's browser. </li>
  </ul>
  
  <p>Since the distributed software will be a unique web server on every individual users' machine, I'm unsure how or even if it is possible, to get a THIRD PARTY SIGNED SSL certificate that won't cause trustworthiness errors when the user connects to it via the web browser. Of course it can use self-signed SSL certs but the idea is to avoid the browser warnings so that the end users will implicitly "trust" data coming from their own application running its webserver over SSL.</p>
  
  <p>Is this possible?</p>