Knowledge Base
Sectigo Certificate Manager (SCM) Error “Anchor Certificate details are different”
When requesting a certificate, when approving a certificate, or in an API call: Customers may encounter one of the following Anchor certificate errors, in the Sectigo Certificate Manager (SCM) portal.
- Anchor certificate address mismatch
- Anchor certificate address details are different
An anchor certificate will pre-validate the organization for future certificate requests.
Note: There is only one OV anchor certificate that can be applied to each organization.
This procedure does not change our current certificate ordering process but is simply here to help make certificate processing more efficient.
Note: The OV Anchor is NOT an actual certificate that can be used.
Common reasons why someone would receive the above Anchor Certificate errors are:
- Details mismatch between the organization details in SCM and the OV Anchor in the Sectigo back-end system.
- Details mismatch between the CSR and the org details/Anchor.
Note: If there is no State documented then it should be left blank.
If the State is blank in the organization details, the State in the CSR must be blank.
You can use OpenSSL or MMC to create a custom CSR with a blank State field.
Tips to troubleshoot the issue:
- When requesting a certificate, always ensure the CSR details match the Organization details.
- Organization details cannot be different than the Anchor details.
Please consult the MRAO or RAO admin to verify the details.
If you have verified the tips above and your issue persists, please contact Sectigo Technical Support for additional assistance
Select “SCM Support” as the reason on the ticket.
You can also use this utility to decode the CSR https://secure.sectigo.com/utilities/decodeCSR.html
Need help?
Need help making a purchase? Contact us today to get your certificate issued right away.
Live chat
Click the button below or click "Chat with an Expert" to start chatting with us now!
