Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
| Note |
|---|
The EUI component is marked for deletion in future releases of CM. Customers that use EUI are encouraged to switch to Certificate Manager (CM) REST API, as it provides the same functions. |
With the Enrollment User Interface (EUI) , an end user or administrator can use a web browser to request to request certificates.
The standard configuration supports certificates installed in web browsers or Nexus Personal Desktop Client, server certificates server certificates and soft tokens. Protocol Gateway provides additional security by the option to require the user to be a be a CM Officer.
| Code Block | ||
|---|---|---|
| ||
<url>/pgwy/request/ |
The standard configuration supports certificate requests for the following usages:
certificates installed in a web browser (thekeygen tag or CertEnroll)- certificates installed in Nexus Personal (
regUtilPluginObject) - server certificates, for example, TLS server certificates, in (PKCS#10 format)
- soft tokens , for example in PKCS#12 format or (PKCS#12, Java key store etc.)
For server certificates, the administrator can select either binary or text as type of response and either PKCS#7 certificates only, with optional issuer chain, or X.509 as certificate encoding.
| Note |
|---|
| Access to the web pages located at <url>/pgwy/request/ cannot be disabled in eui.properties. The HTML files are located in the request folder of the unpacked web application and are served by Tomcat. |
This article includes updates for CM 8.7.1