.nh .TH pki-tps-connector 5 "May 6, 2014" PKI "PKI TPS Profile Configuration" .SH NAME .PP pki-tps-profile - PKI TPS Profile Configuration .SH LOCATION .PP /var/lib/pki/\fIinstance\fP/conf/tps/CS.cfg .SH DESCRIPTION .PP Token profiles are defined using properties in the TPS configuration file. .SS Enrollment Operation For CoolKey .PP The following property sets the size of the key the token should generate: .PP .RS .nf op.enroll..keyGen..keySize=1024 .fi .RE .PP The maximum value is 1024. .PP The following properties specify the PKCS11 attributes to set on the token: .PP .RS .nf op.enroll..keyGen..keyCapabilities.encrypt=false op.enroll..keyGen..keyCapabilities.sign=true op.enroll..keyGen..keyCapabilities.signRecover=true op.enroll..keyGen..keyCapabilities.decrypt=false op.enroll..keyGen..keyCapabilities.derive=false op.enroll..keyGen..keyCapabilities.unwrap=false op.enroll..keyGen..keyCapabilities.wrap=false op.enroll..keyGen..keyCapabilities.verifyRecover=true op.enroll..keyGen..keyCapabilities.verify=true op.enroll..keyGen..keyCapabilities.sensitive=true op.enroll..keyGen..keyCapabilities.private=true op.enroll..keyGen..keyCapabilities.token=true .fi .RE .PP The following property specifies the CUID shown in the certificate: .PP .RS .nf op.enroll..keyGen..cuid_label .fi .RE .PP The following property specifies the token name: .PP .RS .nf op.enroll..keyGen..label .fi .RE .PP The following variables can be used in the token name: .RS .IP \(bu 2 \fB$pretty_cuid$\fP - Pretty Print CUID (i.e. 4090-0062-FF02-0000-0B9C) .IP \(bu 2 \fB$cuid$\fP - CUID (i.e. 40900062FF0200000B9C) .IP \(bu 2 \fB$msn$\fP - MSN .IP \(bu 2 \fB$userid$\fP - User ID .IP \(bu 2 \fB$profileId$\fP - Profile ID .RE .PP All resulting labels for co-existing keys on the same token must be unique. .PP The following property determines whether TPS will overwrite key and certificate if they already exist: .PP .RS .nf op.enroll..keyGen..overwrite=true|false .fi .RE .PP The following properties specify name PKCS11 object IDs: .PP .RS .nf op.enroll..keyGen..certId=C1 op.enroll..keyGen..certAttrId=c1 op.enroll..keyGen..privateKeyAttrId=k2 op.enroll..keyGen..publicKeyAttrId=k3 op.enroll..keyGen..privateKeyNumber=2 op.enroll..keyGen..publicKeyNumber=3 .fi .RE .PP Lower case letters signify objects containing PKCS11 object attributes in the format described below: .RS .IP \(bu 2 \fBc\fP - An object containing PKCS11 attributes for a certificate. .IP \(bu 2 \fBk\fP - An object containing PKCS11 attributes for a public or private key .IP \(bu 2 \fBr\fP - An object containing PKCS11 attributes for an "reader". .RE .PP Upper case letters signify objects containing raw data corresponding to the lower case letters described above. For example, object \fBC0\fP contains raw data corresponding to object \fBc0\fP\&. .RS .IP \(bu 2 \fBC\fP - This object contains an entire DER cert, and nothing else. .IP \(bu 2 \fBK\fP - This object contains a MUSCLE "key blob". TPS does not use this. .RE .PP The following properties specify the algorithm, the key size, the key usage, and which PIN user should be granted: .PP .RS .nf op.enroll..keyGen..alg=2 op.enroll..keyGen..keySize=1024 op.enroll..keyGen..keyUsage=0 op.enroll..keyGen..keyUser=0 .fi .RE .PP The valid algorithms are: .RS .IP \(bu 2 \fB2\fP - RSA .IP \(bu 2 \fB5\fP - ECC .RE .PP For ECC, the valid key sizes are 256 and 384. .PP Use privilege of the generated private key, or 15 if all users have use privilege for the private key. Valid usages: (only specifies the usage for the private key) .RS .IP \(bu 2 \fB0\fP - default usage (Signing only for this APDU) .IP \(bu 2 \fB1\fP - signing only .IP \(bu 2 \fB2\fP - decryption only .IP \(bu 2 \fB3\fP - signing and decryption .RE .PP The following property determines whether to enable writing of PKCS11 cache object to the token: .PP .RS .nf op.enroll..pkcs11obj.enable=true|false .fi .RE .PP The following property determines whether to enable compression for writing of PKCS11 cache object to the token: .PP .RS .nf op.enroll..pkcs11obj.compress.enable=true|false .fi .RE .PP The following property determines the maximum number of retries before blocking the token: .PP .RS .nf op.enroll..pinReset.pin.maxRetries=127 .fi .RE .PP The maximum value is 127. .PP There is a special case of tokenType userKeyTemporary. Make sure the profile specified by the profileId to have short validity period (e.g. 7 days) for the certificate. .PP .RS .nf op.enroll.userKey.keyGen..publisherId=fileBasedPublisher op.enroll.userKeyTemporary.keyGen..publisherId=fileBasedPublisher .fi .RE .PP The folowing property describes the scheme used for recovery: .PP .RS .nf op.enroll..keyGen..recovery..scheme=GenerateNewKey .fi .RE .PP The three recovery schemes supported are: .RS .IP \(bu 2 \fBGenerateNewKey\fP - Generate a new cert for the encryption cert. .IP \(bu 2 \fBRecoverLast\fP - Recover the most recent cert for the encryption cert. .IP \(bu 2 \fBGenerateNewKeyandRecoverLast\fP - Generate new cert AND recover last for encryption cert. .RE .SS Token Renewal .PP The following properties are used to define token renewal: .PP .RS .nf op.enroll..renewal.* .fi .RE .PP For each token in TPS UI, set the following to trigger renewal operations: .PP .RS .nf RENEW=YES .fi .RE .PP Optional grace period enforcement must coincide exactly with what the CA enforces. .PP In case of renewal, encryption certId values are for completeness only, server code calculates actual values used. .SS Format Operation For tokenKey .PP The following property determines whether to update applet if the token is empty: .PP .RS .nf op.format..update.applet.emptyToken.enable=false .fi .RE .PP The property is applicable to: .RS .IP \(bu 2 CoolKey .IP \(bu 2 HouseKey .IP \(bu 2 HouseKey with Legacy Applet .RE .SS Certificate Chain Imports .PP .RS .nf op.enroll.certificates.num=1 op.enroll.certificates.value.0=caCert op.enroll.certificates.caCert.nickName=caCert0 pki-tps op.enroll.certificates.caCert.certId=C5 op.enroll.certificates.caCert.certAttrId=c5 op.enroll.certificates.caCert.label=caCert Label .fi .RE .SS Pin Reset Operation For CoolKey .PP The following property determines whether to update applet if the token is empty: .PP .RS .nf op.pinReset..update.applet.emptyToken.enable=false .fi .RE .PP The property is not applicable to: .RS .IP \(bu 2 HouseKey .IP \(bu 2 HouseKey with Legacy Applet .RE .SH SEE ALSO .PP \fBpki-tps-profile(1)\fP .SH AUTHORS .PP Dogtag PKI Team <devel@lists.dogtagpki.org>\&. .SH COPYRIGHT .PP Copyright (c) 2014 Red Hat, Inc. This is licensed under the GNU General Public License, version 2 (GPLv2). A copy of this license is available at http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt.