Creating the Certificate Key Store for SSL
If you have a production-ready SSL certificate, it is easiest to store it in a keystore.pfx file that is saved in %WILDFLY_HOME%\standalone\configuration\keystore.pfx. If you don't have a production ready server certificate, then you can either create a temporary self-signed one using cert.cmd, to get you started with testing, or buy a production certificate from, for example: https://www.globalsign.com/en/ssl/.
...
| Code Block | ||
|---|---|---|
| ||
cd /D "%PROGRAMFILES%\Ubisecure\customerid\tools"
cert.cmd |
| Warning |
|---|
If cert.cmd fails at JAVA_HOME check even if it is defined correctly, remove Java checks from cert.cmd by editing it using your favorite text editor. |
Successful execution will return Creating localhost keystore %WILDFLY_HOME%\standalone\configuration\keystore.pfx
...
The command has run successfully if the output shows {"outcome" => "success"}.
Setting Up Audit and Diagnostic logging
Starting from Ubisecure CustomerID 5.0.x, logging is managed centrally via the WildFly Java EE container. The script setup-logging.cmd contacts WildFly management port and then sets up logging configuration to redirect Ubisecure CustomerID specific log entries to separate files. To set up logging, run the following commands in a command prompt:
...