Skip to main content

Establishment of HSM Connectivity

Open a command shell and utilize the comand line tool ppin to:

  • manage the connection credentials for secure HSM communication,
    • set the proxy password (only for CloudHSM),
    • fetch the permanent secret from HSM,
  • test HSM and partition connectivity (assuming the permanent secret was already fetched),
  • list the connected partitions
  • retrieve the partition log from configured HSMs (if allowed by HSM configuration),
  • show the installed provider version.
info

For the connection establishment of the Primus PKCS#11 Provider installed on the CyberArk PAM with the on-premises HSM or CloudHSM system obtain the credentials from your HSM administrator or CloudHSM Support: pkcs11-password, setup-password, and additionally for CloudHSM proxy-password.

Setup Connection with on-premise Primus HSM​

Setup Connection with CloudHSM​

Example Configuration​

Following our example, the connection establishment steps illustrate connecting to the partition named DEMO_PARTITION residing on the CloudHSM service with the proxy user name SERVICE_USER.

Set Proxy Password​

For CloudHSM, all connections undergo authentication on a proxy before being forwarded to the HSM. Therefore, the Service Proxy Password must be configured prior to retrieving the HSM permanent secret. Execute the below ppin tool command in a command shell.

tip

If you're setting up the connection with an on-premises Primus HSM, you can skip this step.

ppin -p -e SERVICE_USER

********************
Primus Permanent PIN
********************
Provide proxy password for 'SERVICE_USER' : <enter Service Proxy Password, no echo>

********************
Primus Permanent PIN
********************
[01] slot-id 0:    user 'DEMO_PARTITION'    permanent secret: MISSING
[02] slot-id 0:    user 'DEMO_PARTITION'    permanent secret: MISSING
[01] service/proxy user 'SERVICE_USER' permanent secret: Configured
[02] service/proxy user 'SERVICE_USER' permanent secret: Configured

Retrieving Permanent Secret​

Retrieve the permanent secret for DEMO_PARTITION via the service proxy, by using the ppin tool with User Setup password and PKCS#11 password:

ppin -a -e DEMO_PARTITION

********************
Primus Permanent PIN
********************
Provide setup password for 'DEMO_PARTITION':  <enter User Setup Password, no echo>
Provide PKCS11 password for 'DEMO_PARTITION': <enter PKCS#11 PIN/Password, no echo>
********************
Primus Permanent PIN
********************
[01] slot-id 0:    user 'DEMO_PARTITION'    permanent secret: Configured
[02] slot-id 0:    user 'DEMO_PARTITION'    permanent secret: Configured
[01] service/proxy user 'SERVICE_USER' permanent secret: Configured
[02] service/proxy user 'SERVICE_USER' permanent secret: Configured