000021909 - Error: 'Duplicate Certificate Name' while vetting SSL server certificates in RSA Keon Certificate Authority

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000021909
Applies ToKeon Certificate Authority 6.5.1
IssueError: "Duplicate Certificate Name" while vetting SSL server certificates in RSA Keon Certificate Authority
The following page shows on the browser:

    Duplicate Certificate Name
    The name you provided in the previous step has already been assigned to another certificate. Please enter another value and try again.
    Certificate Name:  <input-field-with-suggested-value> R
    Note: the default value provided above was available when this page was generated, and is very likely to be acceptable.
    <<Back>   <Next>>
CauseCertificate names are not mandatory; however, they can be very useful for setting up web server ACL rules. For ease of reference, it is recommended that it be the same value as the common name when possible. If you add a certificate name, it must be unique among all certificates issued by the same CA. Keon CA tests the uniqueness of the name, and requests a new name if it is not unique.

You can add a certificate name after the certificate is issued and to certificates upgraded from a previous version of Keon CA without reissuing the certificate. Simply view the issued certificate and click the Add Certificate Name button.
ResolutionEither use unique values for the Certificate Name field, or do not use (leave blank) the Certificate Name when vetting requests.

NOTE: This information is also noted in the RSA Keon Certificate Authority 6.5.1 Administrator's Guide, page 78.
WorkaroundThe vettor entered a value for the "Certificate Name" field when vetting a certificate request
Legacy Article IDa25658