Installation fails due to X.509 private key configuration

If the Application Server is configured to require an X.509 private key, the Compliance Content installer hangs in the Application Server validation phase. The installer cannot proceed because it creates a new shell on the server, and since the BL_X509_KEY variable is per-session, it is not valid for the new session.

The workaround is to use secadmin on the Application Server to (at least temporarily) create a secure certification, so that passwords are not required. For example:

secadmin -m default -cu root -cp password