How Special Characters in the Name Field Effect Certificates (216947)
The information in this article applies to:
- Microsoft Certificate Server 1.0
- Microsoft Windows NT Server 4.0
This article was previously published under Q216947 SUMMARY
This article describes why, when special characters are included as part
of a name in a certificate, they cause that part of the name to be encoded
as a Unicode string rather than a printable string. This process of
promoting string encoding from Printable to Unicode is fully documented in
the relevant IETF standard (pkix part 1). However, applications written
before the standard may have problems processing certificates,
particularly CA Certificates, that contain Unicode names. Before including
these special characters in a CA certificate name, it is advisable to
confirm that all applications using certificates from a CA can correctly
process certificates containing the Unicode names.
This affects all releases of Microsoft Certificate Server, including
version 1.0 that shipped with the Windows NT Option Pack, the QFE update for Exchange Server, and the SP4 update.
Modification Type: | Major | Last Reviewed: | 11/4/2003 |
---|
Keywords: | kbhowto KB216947 |
---|
|