|Applies To||Keon Certificate Authority 6.5.1|
nCipher Hardware Security Module
|Issue||Keon Certificate Authority with nCipher HSM load sharing|
An nCipher HSM module ignores the Xudad.conf setpin directive when a failover occurs
|Cause||Where more than one nCipher HSM makes up part of a Security world, the first device may be initialized by the "setpin" directive in xudad.conf so that it is not necessary for a operator to input the OCS password when the private key of the CA is used. If the current HSM does a failover to a second HSM, then the OCS password is required to be entered manually on the vetting page.|
This occurs because the current designed behavior for the setpin directive is that it is processed only at the time xudad starts up, and the design of the password processing (for security reasons) has KCA remove all trace once the first nCipher unit is logged into. The net effect is that when the second HSM is activated, it too must have a login.
|Resolution||At the current time, this is the correct behavior for KCA running with multiple HSM devices.|
|Legacy Article ID||a21026|