Cookies are used to collect information about you. Nexus uses this information to give you a better experience of the website (functional) and to count the pages you visit (statistics).
Click OK to give Nexus your consent to use cookies. Read more about Nexus' cookie policy.
To issue certificate for PKCS#10 request, see heading "Create a token procedure with storage profile PKCS#10" in Bootstrap Certificate Manager
Generate system key for PIN encryption - Software token
If there are smart cards already pre-personalized in the KGS with an older key ID and these smart cards are still waiting to be personalized, then both the old keys and the new key will be required in the CF service. Two instances of either the pin.file or pin.cert parameters must then be set as described below in this section.
Save the PIN encryption key software token file to a removable media and name it pin.p12.
Save the new PIN encryption certificate to a file on the same removable media and name it pin.cer.
In the CF service, replace the old file <configuration_root>/certs/pin.p12 with the new file pin.p12. If the old file is still required, rename the new file. See Note at the start of the Task.
Configure the PIN encryption software token
The PIN encryption software token must be configured in the CF service (or in all computers running CF in case of a distributed configuration).
In cm.conf:
Set the parameter pin.file to the path and name the new PIN key.
Set the parameter pin.pin to avoid manual intervention during start of CM servers.
Restart the system in order to make the changes take effect.
Generate system key for PIN encryption - Hardware token
The PIN encryption hardware token must be configured in the CF service (or in all computers running CF and CRLF in case of a distributed configuration).
In cm.conf:
Set the parameter pin.cert to a case sensitive string value taken from the Distinguished Name in the TLS server certificate.
Set the parameter pkcs11.<n>, (where <n> is a sequence number for each library) to specify the PKCS #11 libraries that shall be available for use in TLS authentication and that shall be searched for the specified certificate.
Set the parameter pin.pin to avoid manual intervention during start of the CM servers (also called Optional PIN).
Set the parameter pin.nopin=true to avoid showing unnecessary dialogs when the HSM has a PIN pad or if it doesn’t require a PIN code.
Restart the system in order to make the changes take effect.
Install PIN encryption certificate in the KGS
In the Key Generation System (KGS), replace the old certificate file <install_root>/certs/pin.crt with the new certificate file pin.cer.