Red Hat CERTIFICATE SYSTEM 8 - DEPLOYMENT Deployment Manual page 57

Protocol
Lightweight Directory Access Protocol (LDAP)
v2, v3
Public-Key Cryptography Standard (PKCS) #7
Public-Key Cryptography Standard (PKCS) #10
Public-Key Cryptography Standard (PKCS) #11
Secure Sockets Layer (SSL) 2.0 and 3.0 and
Transport Layer Security (TLS)
Security-Enhanced Linux
Simple Certificate Enrollment Protocol (SCEP)
UTF-8
Supported Security and Directory Protocols
Description
A directory service protocol designed to run over
TCP/IP and across multiple platforms. LDAP is
a simplified version of Directory Access Protocol
(DAP), used to access X.500 directories. LDAP
is under IETF change control and has evolved to
meet Internet requirements.
An encrypted data and message format
developed by RSA Data Security to represent
digital signatures, certificate chains, and
encrypted data. This format is used to deliver
certificates to end entities.
A message format developed by RSA Data
Security for certificate requests. This format is
supported by many server products.
Specifies an API used to communicate
with devices such as hardware tokens that
hold cryptographic information and perform
cryptographic operations.
A set of rules governing server authentication,
client authentication, and encrypted
communication between servers and clients.
Security-enhanced Linux, or SELinux, is a set of
security protocols enforcing mandatory access
control on Linux system kernels. This was
developed by the United States National Security
Agency to keep applications from accessing
confidential or protected files through lenient or
flawed access controls.
A protocol designed by Cisco to specify a way
for a router to communicate with an RA or CA
for router certificate enrollment. SCEP defines
two modes of operation: RA mode and CA mode.
Certificate System supports CA mode, where
the the request is encrypted with the CA signing
certificate.
The certificate enrollment pages support all
UTF-8 characters for specific fields (common
name, organizational unit, requester name,
and additional notes). The certificates will be
generated with the UTF-8 strings correctly used
in the subject names and other fields, and the
UTF-8 strings are searchable and correctly
display in the CA, OCSP, and DRM end user and
agents services pages.
This UTF-8 support does not extended to
internationalized domain names, like in email
addresses.
47