Error: "No stored certificate request matches this certificate" when installing a SSL/TLS certificate in Messaging Gateway
Article ID: 152732
Updated On:
Products
Issue/Introduction
Attempting to import a third party signed TLS certificate results in the error "No stored certificate request matches this certificate."
Cause
This message is returned when a certificate import file cannot be matched to either an existing certificate signing request (CSR), or an existing certificate in the database. This can be due to:
- The certificate file of the wrong format (e.g. pk7 formatted rather than the required x509 format)
- A failure to include both the certificate and matching a private key in the import file
- A wildcard certificate with no associated CSR or private key in the SMG Control Center.
- The import file contains an encrypted private key
Resolution
Ensuring that the Signed Certificate Matches the Certificate Signing Request
WARNING: All files below are examples; do not use them. Please use your own CSR and certificate.
-
- Ensure you have the actual CSR file from the appliance. You can only see it when creating the request, and must be saved locally after creation.
Example CSR:-----BEGIN NEW CERTIFICATE REQUEST-----
MIIBzDCCATUCAQAwgYsxJDAiBgkqhkiG9w0BCQEWFWZZZZZZZZ9saXBza2lAbW9u
eC5ldTEXMBUGA1UEAxMObWFpbDAxLm1vbnguZXUxEDAOBgNVBAgTB0lyZWxhbmQx
DzZZZZNVBAcTBkR1YmxpbjELMAkGA1UEBhMCSUUxCzAJBgNVBAsTAml0MQ0wCwYD
VQQKEwRtb254MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQChmgiTNm+5FzpS
gTXvTr7Y4njrJdrF7rZZZZZZZZZZZZZZZZZZZZZZenFHIL+l2Tp8j9IWjPE7pCs5
SdTP9HzhOqxg4IzRHpaIz5LhR8Mbu1S8tMvrPNZqEbCsYsq3JTfPRcy/tJCgXBNx
vzNN784Px74/SMibp0pfAS2mVH4poQIDAQABoAAwDQYJKoZIhvcNAQEEBQADgYEA
SL7SG4zmBLTgDesLZZZZZZZZZZZZZZZZK9CaCoWwB/eAQ3fdbcSPTuJXjonpGGJw
4TzwXVBl5068cqvtEjI1bEl3WonncajiiA3pprvGp+HXbNNyJtovprWay33Kldms
DhhzSV7ijERdjOVGvnnl09tnZLnQLNtQ9CF3bKfqnqo=
-----END NEW CERTIFICATE REQUEST-----
- Ensure you have the certificate file generated by the CA from the CSR in step 1:
Example x509/PEM certificate:-----BEGIN CERTIFICATE-----
MIIFSTCCBDGgAwIBAgIQS1wGA8JSt8ZZZZZZZZZZZZZZZZZZhkiG9w0BAQUFADCB
yzELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTAwLgYDVQQL
EydGb3IgVGVzdCBQdXJwb3NlcyBPbmx5LiAgTm8gYXNzdXJhbmNlcy4xQjBABgNV
BAsTOVRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vY3Bz
L3Rlc3RjYSAoYykwOTEtMCsGA1UEAxMkVmVyaVNpZ24gVHJpYWwgU2VjdXJlIFNl
cnZlciBDQSAtIEcyMB4XDTEwMDkwOTAwMDAwMFoXDTEwMDkyMzIzNTk1OVowgaEx
CzAJBgNVBAYTAklFMRAwDgYDVQQIEwdJcmVsYW5kMQ8wDQYDVQQHFAZEdWJsaW4x
DTALBgNVBAoUBG1vbngxCzAJBgNVBAsUAml0MTowOAYDVQQLFDFUZXJtcyBvZiB1
c2UgYXQgd3d3LnZlcmlzaWduLmNvbS9jcHMvdGVzdGNhIChjKTA1MRcwFQYDVQQD
FA5tYWlsMDEubW9ueC5ldTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAoZoI
kzZvuRc6UoE1ZZZZZZZZZZZZZZZZZZZZZZZLbT/x6SQRwc7SJXpxRyC/pdk6fI/S
FozxO6QrOUnUz/R84TqsYOCM0R6WiM+S4UfDG7tUvLTL6zzWahGwrGLKtyU3z0XM
v7SQoFwTcb8zTe/OD8e+P0jIm6dKXwEtplR+KaECAwEAAaOCAdMwggHPMAkGA1Ud
EwQCMAAwCwYDVR0PBAQDAgWgMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9TVlJU
cmlhbC1HMi1jcmwudmVyaXNpZ24uY29tL1NWUlRyaWFsRzIuY3JsMEoGA1UdIARD
MEEwPwYKYIZIAYb4RQEHFTAxMC8GCCsGAQUFBwIBFiNodHRwczovL3d3dy52ZXJp
c2lnbi5jb20vY3BzL3Rlc3RjYTAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUH
AwIwHwYDVRZZZZZZZZZZZZZZZZZZZZZZBiy3to7aEGZgbuUwdAYIKwYBBQUHAQEE
aDBmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wPgYIKwYB
BQUHMAKGMmh0dHA6Ly9TVlJUcmlhbC1HMi1haWEudmVyaXNpZ24uY29tL1NWUlRy
aWFsRzIuY2VyMG4GCCsGAQUFBwEMBGIwYKFeoFwwWjBYMFYWCWltYWdlL2dpZjAh
MB8wBwYFKw4DAhoEFEtruSiWBgy70FI4mymsSweLIQUYMCYWJGh0dHA6Ly9sb2dv
LnZlcmlzaWduLmZZZZZZZZZZZZZZZZZZZjANBgkqhkiG9w0BAQUFAAOCAQEAZYq3
ZI9mi487cjH6Y2kuOoUReidD2+X7l02rHdnPmeEOuQI+hUSJ6+GoQdV46aV4fN73
+e/c4g7k9tnAESfLBf7JokgKp7MNXh3d06Iejgu+IMsJc4orehlghtIXEvaGLzoq
wUxfw/NqnEGgK45g6M9Q//BLY8WeWSG2FWBeHDRDiE0rQghs9eR8gOPQU2w/gij9
W1Rck95aVbu24A4kXk5qDqD1z+u9zSWX6DIX/wbJhAM6DVxoziIO4ES+A/bOWy+A
193dM9rv3ACKUxtVPG4ZrrzTURrUFmFL02OirejhmO63yUHBm7GwQXQBBc2Ne7RQ
WNcaWUo+PVfA5C2Q5g==
-----END CERTIFICATE-----
- Use the following openssl command to the display contents of CSR, where "cert.csr" is your CSR file:
openssl req -text -noout -verify -in cert.csr
- Use the following openssl command to display contents of the certificate, where cert.pem is your certificate file:
openssl x509 -in cert.pem -text -noout
- Compare the sections called "Modulus" and "Expotent" in both the CSR and certificate file; they should be identical. If not, this may mean that the certificate has been created from a different CSR.
- Review the "Subject" section in both the CSR and certificate. Verify the information matches.
- Ensure you have the actual CSR file from the appliance. You can only see it when creating the request, and must be saved locally after creation.
Ensuring that the Import File Includes Both Certificate and Key
The import file should include two sections:
-
- The base64 encoded certificate data
- The base64 encoded RSA private key data
Visually, the import file should have data and section boundaries that appear as follows
-----BEGIN CERTIFICATE-----
MIIFSTCCBDGgAwIBAgIQS1wGA8JSt8ZZZZZZZZZZZZZZZZZZhkiG9w0BAQUFADCB
...
W1Rck95aVbu24A4kXk5qDqD1z+u9zSWX6DIX/wbJhAM6DVxoziIO4ES+A/bOWy+A
193dM9rv3ACKUxtVPG4ZrrzTURrUFmFL02OirejhmO63yUHBm7GwQXQBBc2Ne7RQ
WNcaWUo+PVfA5C2Q5g==
-----END CERTIFICATE----------BEGIN RSA PRIVATE KEY-----
FSmHIRHsy1B1wkaXV3bAhRgRN0/RyshmG1CxSpmAx7VIp3HIGtNdi7BzMeUI+GjV
...
ywZ1IOnfmIk38QwzmvtyjQ8btvUWVTmZ8yEaVbf/nIdQLtoWCXrhKLbj9rHd
-----END RSA PRIVATE KEY-----
Ensuring that the Private Key is not Encrypted
An encrypted private key has the following key boundaries:
-----BEGIN ENCRYPTED PRIVATE KEY----------END ENCRYPTED PRIVATE KEY-----
If the private key is encrypted you will need to use openssl to remove the password and encryption from the private key. You will be prompted for the private key password set when it was generated:
openssl rsa --in encrypted.key --out rsa.key
Additional Information
Search keywords: Certificate Authority, Certificate, Import, Failed
Feedback
