KRATool does not support serialno field in CA/TPS KRA enrollment requests
Steps to Reproduce:
1. 2 CA and KRA were instances configured with CS 9.1 packages 2. certutil -L -d /var/lib/pki/pki-kra1/alias/ -n "storageCert cert-pki-kra1 KRA" -a > /export/drmtooltestdata/pki1/kra1-storage.cert 3. /usr/lib64/dirsrv/slapd-dir1/db2ldif -n "pki-kra1-KRA" -a /export/drmtooltestdata/pki1/kra1-dbconfig.ldif 4. cp /var/lib/pki-kra1-sep6/alias/*.db /export/drmtooltestdata/pki1 5. certutil -L -d /var/lib/pki/pki-kra2/alias/ -n "storageCert cert-pki-kra2 KRA" -a > /export/drmtooltestdata/pki2/kra2-storage.cert 6. cp /export/drmtooltestdata/pki2/kra2-storage.cert /export/drmtooltestdata/pki1 [root@pki1 ~]# KRATool -kratool_config_file /usr/share/pki/java-tools/KRATool.cfg -source_ldif_file /tmp/kra1-dbconfig.ldif -target_ldif_file /tmp/kra1-kra2.ldif -log_file /tmp/KRATool.log -source_pki_security_database_path /tmp/drmtool -source_storage_token_name 'Internal Key Storage Token' -source_storage_certificate_nickname 'storageCert cert-topology-02-KRA KRA' -target_storage_certificate_file /tmp/drmtool/kra2-storage.cert -append_id_offset 100000000000 -source_kra_naming_context 'nightcrawler.idmqe.lab.eng.bos.redhat.com-pki-kra' -target_kra_naming_context 'ibm-x3650m4-02-vm-02.lab.eng.bos.redhat.com-pki-kra' -process_requests_and_key_records_only BEGIN "KRATool -kratool_config_file /usr/share/pki/java-tools/KRATool.cfg -source_ldif_file /tmp/kra1-dbconfig.ldif -target_ldif_file /tmp/kra1-kra2.ldif -log_file /tmp/KRATool.log -source_pki_security_database_path /tmp/drmtool -source_storage_token_name 'Internal Key Storage Token' -source_storage_certificate_nickname 'storageCert cert-topology-02-KRA KRA' -target_storage_certificate_file /tmp/drmtool/kra2-storage.cert -append_id_offset 100000000000 -source_kra_naming_context 'nightcrawler.idmqe.lab.eng.bos.redhat.com-pki-kra' -target_kra_naming_context 'ibm-x3650m4-02-vm-02.lab.eng.bos.redhat.com-pki-kra' -process_requests_and_key_records_only" . . . PROCESSING KRATOOL CONFIG FILE: ............................. FINISHED. SUCCESSFULLY processed kratool config file! Initializing source PKI security databases in '/tmp/drmtool'. Retrieving token from CryptoManager. Retrieving source storage token called 'Internal Key Storage Token'. Retrieving source storage cert with nickname of 'storageCert cert-topology-02-KRA KRA'. BEGIN: Obtaining the private key from the source storage token . . . Enter password for Internal Key Storage Token FINISHED: Obtaining the private key from the source storage token. BEGIN: Obtaining the public key from the target storage certificate . . . FINISHED: Obtaining the public key from the target storage certificate. PROCESSING: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx...........................................................................................................!.....ERROR: Mismatched record field='serialno:' for record type='enrollment'! FAILED converting source LDIF file --> target LDIF file! FINISHED "KRATool -kratool_config_file /usr/share/pki/java-tools/KRATool.cfg -source_ldif_file /tmp/kra1-dbconfig.ldif -target_ldif_file /tmp/kra1-kra2.ldif -log_file /tmp/KRATool.log -source_pki_security_database_path /tmp/drmtool -source_storage_token_name 'Internal Key Storage Token' -source_storage_certificate_nickname 'storageCert cert-topology-02-KRA KRA' -target_storage_certificate_file /tmp/drmtool/kra2-storage.cert -append_id_offset 100000000000 -source_kra_naming_context 'nightcrawler.idmqe.lab.eng.bos.redhat.com-pki-kra' -target_kra_naming_context 'ibm-x3650m4-02-vm-02.lab.eng.bos.redhat.com-pki-kra' -process_requests_and_key_records_only".
Additional Info:
See display of log in associated bug.
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: critical - Issue set to the milestone: 10.5
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1465620
Metadata Update from @mharmsen: - Issue priority set to: major (was: critical)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
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/2887
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.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.