Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In order to meet the CA/B guidelines, it is essential that all location information is correctly entered in certificate fields.  We recommend ONLY completing the Locality and Country information where possible - the more information entered, the more likelihood there is that something will go wrong.  Certificates may be revoked for something as small as the different between Noord Holland and Noord-Holland in the State field.  https://en.wikipedia.org/wiki/ISO_3166-2 is generally used a guide to the correct way to add information, but may not be completely consistent with official local sources given the nature of wikipedia.  The most common problem is with incorrect use of State - we recommend not filling this in wherever possible.  If this field is populated, please make sure it matches the ISO guidelines as described in the "sub-divisons" column in the cited wikipedia page.  Do not abbreviate names (N-Holland is not allowed), or add excess data.

Q: How do I deal with non-ACII characters for IGTF certificates?

IGTF certificates must not  contain non-ACII characters.  There are several ways to manage this:

  • If your organisation name contains non-ASCII characters, please enter an ASCII version in the "Secondary Organization Name" box under Settings.  E.g. GÉANT Vereniging becomes GEANT Vereniging.
  • Try to limit the fields that you complete for the certificate - it is only necessary to complete Locality and Country.
  • Sectigo are happy to change fields to include ASCII characters once validation has occurred.  Please contact the helpdesk for this.
  • If you would prefer to keep non-ASCII characters within your normal certificates, you can create a second organisation with the same data but with non-ASCII characters completed.  We recommend alerting the helpdesk that this is your intention.