title: Why is using a certificate, made with the MakeCert tool, in production bad?
body: <p>I'm currently working on a project where I've created a CA cert and a couple of child certs to that CA cert. The certificates are going to be used to protect inter-server communication in a SAMLV2 setup so I'm going to have a cert for the identity provider and a cert for the service provider. The user/browser isn't going to validate the certs so it's only the servers that need to trust my custom CA. My cert tree looks something like this:</p>
  
  <ul>
  <li>CustomRootCACert
  
  <ul>
  <li>CustomIdentityProviderCert</li>
  <li>CustomServiceProviderCert</li>
  </ul></li>
  </ul>
  
  <p>Now, I've heard a lot of people saying it's bad to use a home-made certificate in production. But when I ask why, people usually just mutters something about security but never go into the details. Are there any technical reasons not to use my own certs in production? I can't think of any... Of course I realize that if I lose control of my root cert anyone could start creating all sorts of certificates. But in this case they would also have to install the certificates on my servers and configure the saml application to use them. Only then could they start to generate fake saml requests and responses to my applications.</p>
  
  <p>If this is the only problem, this solution (using home-made certs in production) would still be better than the login setup we have today.</p>