Copy these files from the Remote File System (RFS) or another existing HSM client.
Source path (Windows example) | Destination path |
|---|---|
C:\ProgramData\nCipher\Key Management Data\config\card_<hash> | kmdata/config/card_<hash>_<n> |
C:\ProgramData\nCipher\Key Management Data\config\cards_<hash> | kmdata/config/cards_<hash> |
Where:
<n>is the number of cards in the Operator Card Set (OCS).<hash>is the hash of the OCS token.
Run the following command to query for these files.
nfkminfo -cIn the command output, check the number of card files and token hashes. For example:
Cardset list - 1 cardsets: (P)ersistent/(N)ot, (R)emoteab/e/(L)oca/-onlyOperator logical token hash k/n timeout name67Sadb78b8cOdcbda9eabdca2d164393db69ca88 1/1 none-PR OCS According to this output, the HSM configuration includes the following files:
card_67Sadb78b8cOdcbda9eabdca2d164393db69ca88_1cards_67Sadb78b8cOdcbda9eabdca2d164393db69ca88An OCS using two cards would include the following files:
card_67Sadb78b8cOdcbda9eabdca2d164393db69ca88_1card_67Sadb78b8cOdcbda9eabdca2d164393db69ca88_2cards_67Sadb78b8cOdcbda9eabdca2d164393db69ca88