The information in the certificate procedures and key procedures, if any, in the selected token procedure is used to calculate the number of keys, and the key usages, to be generated for the software token. A key archive or key recover request is created for each key procedure in the token procedure. A key pair is generated by the RA for each certificate procedure with a key usage definition that is unique, that is, it is not included in any other key procedure for archiving or certificate procedure. Note |
---|
The RA will only generate local key pairs if the selected procedure contains certificate procedures with a unique key usage definition, compared with the key usage definitions in the key procedures for archiving. Otherwise, all keys are generated or recovered in the server. |
Key algorithm and lengthThe algorithm and key length or Elliptic Curve (EC) named curve of the key pairs to be generated by the RA is selected in the Key Length field. The list of available algorithms and length/named curve pairs is either configured in the ra-key-generation parameter in the local client.conf configuration file, or in the client.ra-key-generation parameter in the cm.conf configuration file on the server. The default configuration contains the following choices: Code Block |
---|
client.ra-key-generation = RSA:2048*, RSA:3072, RSA:4096, RSA:8192, \
EC:brainpoolP256r1, EC:brainpoolP320r1, EC:brainpoolP384r1, EC:brainpoolP512r1, \
EC:secp256r1, EC:secp384r1, EC:secp521r1, \
DSA:1024 |
|