This article describes how to install and configure the Web UI component in Nexus Certificate Manager.
See Certificate Manager Web UI communication flow for a detailed description of the communication between system components.
Prerequisites
-
Certificate Manager (CM 8.15.1) is installed. See Nexus Certificate Manager.
-
Protocol Gateway (PGWY) is installed and configured. See Install Protocol Gateway.
-
PGWY officer (VRO) roles should have “use client” only.
-
CM REST API configuration in Protocol Gateway. See Configure REST API in Protocol Gateway.
-
-
Verify the supported Personal Desktop Client is installed see Instruction to install Personal Desktop client on windows.
-
If required place the windows.zip file under
\Tomcat 10.1\webapps\webui\webui\files\
-
-
Hermod is configure with basic setup and up.
-
Check response “Plugout Message Server”
https://<server-dns>:20400/hermod/rest/ms
-
-
You must configure Protocol Gateway for external authentication against Hermod to use CM Web UI.
-
Assigning other roles to PGWY officer may override the roles & privileges of client WebUI officer.
Prefer container-based setup for Hermod.
The latest version supports Tomcat 11 and Java 25 therefore have a separate supportive installation of Java and Tomcat for .war setup; see Instructions to Install Hermod.
Setup HERMOD with PGWY
-
Verify that prerequisites required endpoints are configured and responding.
-
CM SDK connectivity from PGWY to CM is working, server DNS is configured in TLS cert.
-
Verify that PGWY Officer used for client authentication has limited required roles assigned “use client”.
-
Protocol Gateway (PGWY) ping responding
https://<server-dns>:8443/pgwy/ping
-
-
Handshaking, Create Hermod TLS certificate and P12.
-
In tomcat/server.xml add Connector port="20400" add TLS p12 file in conf folder of tomcat - (path to add in server.xml of tomcat)
<--- HERMOD settings---> <Connector port="20400" protocol="org.apache.coyote.http11.Http11NioProtocol" SSLEnabled="true" defaultSSLHostConfigName="localhost" maxThreads="150" scheme="https" secure="true"> <SSLHostConfig sslProtocol="TLS" protocols="TLSv1.2,+TLSv1.3" hostName="localhost" truststoreFile="conf/new_tls.jks" truststorePassword="1234" certificateVerification="none"> <Certificate certificateKeystoreFile="conf/hermodTLS.p12" certificateKeystorePassword="1234" certificateKeystoreType="PKCS12"/> </SSLHostConfig> </Connector> -
Add boot and issuing CA cert to trust store JKS and java security
keytool -importcert -alias bootcaB -cacerts -storepass changeit -file cacerts/<your_cert.cer>
-
Officer & Personal Desktop setup
-
Issue CM Officer Token using Registration Authority (RA) client.
-
Create a token (webuiAuth.p12) or prepare a smartcard.
-
-
Create an Officer Profile(Webui Officer Profile) using AWB client.
-
With roles “Issue certificates”, “Revoke certificates” and “use clients”.
-
-
Create an Officer (Webui Officer)
-
Add profile (Webui Officer Profile)
-
Add the issued certificate in step 1 to the officer object (webuiAuth.p12 certificate).
-
-
Steps in Personal Desktop app.
-
Import the Officer.p12 and add issuing CA certificate to OS trust store.
-
Or connect smart card.
-
Required Configurations
Install and deploy WAR file for CM Web UI
-
Download cm-web-ui-2.0.2.zip from the Nexus support portal.
-
Unzip and copy webui.war to the "Tomcat/webapps" subdirectory of the Tomcat installation.
-
Restart Tomcat check logs.
-
verify that CM-WEBUI is available at
https://<server-DNS>>:8443/webuiand authenticate using officer.