#2915 keyGen fails when only Identity certificate exists
Closed: fixed Opened by mharmsen.

When enrolling an "admin" token where only a single Identity and Signing certificate exists, keyGen fails.

Steps to Reproduce:

1. Create token/certificate profile to enroll only a single identity and signing certificate.
2. Attempt to enroll token.

Actual results:

[22/Sep/2017:08:22:49][http-bio-62071-exec-4]: TPSEnrollProcessor.generateCertificate: exception:TPSEngine.serverSideKeyGen: Invalid input data!
[22/Sep/2017:08:22:49][http-bio-62071-exec-4]: TPSEnrollProcessor.generateCertificates: ends 
[22/Sep/2017:08:22:49][http-bio-62071-exec-4]: TPSEnrollProcessor.enroll:generateCertificates returned false means cert enrollment unsuccessful
[22/Sep/2017:08:22:49][http-bio-62071-exec-4]: LDAPDatabase: addRecord("20170922082249530000.27")
[22/Sep/2017:08:22:49][http-bio-62071-exec-4]: In LdapBoundConnFactory::getConn()
[22/Sep/2017:08:22:49][http-bio-62071-exec-4]: masterConn is connected: true
[22/Sep/2017:08:22:49][http-bio-62071-exec-4]: getConn: conn is connected true
[22/Sep/2017:08:22:49][http-bio-62071-exec-4]: getConn: mNumConns now 2
[22/Sep/2017:08:22:49][http-bio-62071-exec-4]: LDAPDatabase: adding cn=20170922082249530000.27,ou=Activities,dc=nss-tps-2
[22/Sep/2017:08:22:49][http-bio-62071-exec-4]: returnConn: mNumConns now 3
[22/Sep/2017:08:22:49][http-bio-62071-exec-4]: TPSSession.process: Message processing failed: generateCertificates failed
[22/Sep/2017:08:22:49][http-bio-62071-exec-4]: TPSConnection.write: Writing: s=43&msg_type=13&operation=1&result=1&message=35
[22/Sep/2017:08:22:49][http-bio-62071-exec-4]: TPSSession.process: leaving: result: 1 status: STATUS_ERROR_CONTACT_ADMIN
[22/Sep/2017:08:22:49][http-bio-62071-exec-4]: After session.process() exiting ...

Expected results:

Success

Metadata Update from @mharmsen:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1494591 https://bugzilla.redhat.com/show_bug.cgi?id=1539933
- Custom field type adjusted to None
- Custom field version adjusted to None

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1494591, https://bugzilla.redhat.com/show_bug.cgi?id=1539933 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1494591 https://bugzilla.redhat.com/show_bug.cgi?id=1539933)

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.6)

Checkins:

master:

commit c87d7820f7b1af97134197a23543e9fc4be1aa39 (HEAD -> master, origin/master, origin/HEAD)
Author: Jack Magne jmagne@redhat.com
Date: Mon Jan 15 13:59:33 2018 -0800

Test fix for TPS server side key gen for only identity cert problem.
Change-Id: I15fc1b8a3fa92568aca853f0e89b9e87bbad463d

branch:

commit c1314749b7b3a2a6647aadd6945186833e539da8 (HEAD -> DOGTAG_10_5_BRANCH, origin/DOGTAG_10_5_BRANCH)
Author: Jack Magne jmagne@redhat.com
Date: Mon Jan 15 13:59:33 2018 -0800

Test fix for TPS server side key gen for only identity cert problem.
Change-Id: I15fc1b8a3fa92568aca853f0e89b9e87bbad463d
(cherry picked from commit c87d7820f7b1af97134197a23543e9fc4be1aa39)

commit 35936a8478c931b59a0df4291dc16ffe3dfe4070 (tag: v10.5.10)

Metadata Update from @jmagne:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.11 (was: 10.5)

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.5.11-1.fc27

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/3033

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata