Bug #1318
closed
  
Certificate error: certificate subject does not match signing request subject
 
        
        Added by Zinger daZinger over 14 years ago.
        Updated about 14 years ago.
        
  
  
  
  Description
  
  Hi - I'm trying to apply a certificate from StartCom/Startssl.com to my PFSense 2.0-RC1 (amd64)  -built on Wed Mar 2 12:54:13 EST 2011 - instance.
	I'm getting this error:
	The certificate subject 'emailAddress=user@domain.com, description=abc123xxxyyyzzz, OU=StartCom Free Certificate Member, O=Persona Not Validated, CN=host.domain.com, C=US' does not match the signing request subject.
   
 
  
  Files
  
 
  
  
    
    
    
    Can you show the subject that is displayed on pfSense screen of the signing request?
 
     
   
  
  
    
    
    
    
    I am having the same issue.  I tried to use a register.com SSL cert, which has intermediate CAs.  Upon getting the cert from register.com, pfsense complains about "does not match the signing request subject".
	My pfsense version info:
2.0-RC1 (amd64)
built on Sat Mar 26 00:18:39 EDT 2011
 
     
   
  
  
    
    
    
    
    I can also confirm this issue.
	2.0-RC1 (i386) 
built on Mon Mar 28 16:09:59 EDT 2011
	The CSR (included) was signed using the CACert Class 1 root certificate. However, pfSense refuses the signed certificate. Getting
	The certificate subject 'CN=stormfront-noord.int.storm.vu' does not match the signing request subject.
	(CACert removes most fields, so pfSense is only complaining about the CN field)
	CSR included. For obvious reasons, certificate not included.
 
     
   
  
  
    
    
    
    Also confirmed with RapidSSL with GeoTrust as the intermediate CA.
	2.0-RC1 (amd64) 
built on Thu Apr 14 11:13:23 EDT 2011
 
     
   
  
  
    
    
    
    I can also confirm this is the case with PositiveSSL's issued from Comodo.
	2.0-RC1 (amd64) 
built on Thu Apr 28 03:47:19 EDT 2011
 
     
   
  
  
  
  
    
    
    
    Ermal - that is exactly what is in the works. Check ticket #1438 - this ticket can probably be closed in favor of that one, which is actually the solution for this ticket once implemented.
 
     
   
  
  
    
    
    
    
       - Status changed from New to Feedback
 
    
    Can anyone reproduce this since #1438 has been fixed/closed?
 
     
   
  
  
    
    
    
    
       - Status changed from Feedback to Resolved
 
    
    
     
   
  
 
  
  
 
Also available in:  Atom
  PDF