TPS instance configured with client side key generation has some token types which has server side key generation enabled
Steps to Reproduce:
1. TPS configuration file [DEFAULT] pki_instance_name = topology-05-TPS pki_https_port = 25443 pki_http_port = 25080 pki_token_password = Secret123 pki_admin_password = Secret123 pki_hostname = pki1.example.com pki_security_domain_hostname = pki1.example.com pki_security_domain_https_port = 20443 pki_security_domain_name = topology-05_Foobarmaster.org pki_security_domain_password = Secret123 pki_client_dir = /opt/topology-05-TPS pki_client_pkcs12_password = Secret123 pki_backup_keys = True pki_backup_password = Secret123 pki_ds_password = Secret123 pki_ds_ldap_port = 8389 pki_client_database_password = Secret123 [Tomcat] pki_ajp_port = 25009 pki_tomcat_server_port = 25005 [TPS] pki_import_admin_cert = False pki_ds_hostname = pki1.example.com pki_authdb_basedn = ou=People,dc=example,dc=org pki_authdb_hostname=pki1.example.com pki_authdb_port=8389 pki_ca_uri=https://pki1.example.com:20443 pki_tks_uri=https://pki1.example.com:23443 pki_kra_uri=https://pki1.example.com:21443 pki_admin_nickname=PKI TPS Administrator for Example.Org
Actual results:
I see the following in TPs CS.cfg op.enroll.externalRegAddToToken.keyGen.encryption.serverKeygen.enable=true op.enroll.delegateISEtoken.keyGen.encryption.serverKeygen.enable=true op.enroll.delegateIEtoken.keyGen.encryption.serverKeygen.enable=true
Expected results:
op.enroll.externalRegAddToToken.keyGen.encryption.serverKeygen.enable=false op.enroll.delegateISEtoken.keyGen.encryption.serverKeygen.enable=false op.enroll.delegateIEtoken.keyGen.encryption.serverKeygen.enable=false
Per PKI Bug Council of 06/23/2016:
Solution will be provided by PKI TRAC Ticket #2360 - (TPS) externalReg: Investigated why extra keytype is needed in TPS profile for recovering certs
Metadata Update from @rpattath: - Issue set to the milestone: 10.3.4
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2492
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.