dogtagpki

#2631 externalRegRecover does not support multiple KRA instances
Closed: fixed Opened by mharmsen.

Closed: fixed
Reopen Issue

When attampting to recover key from additional KRA instance, TPS defaults to
hard-coded kra1 connection.

Steps to Reproduce:

1. Create two kra instances, kra1 and kra2
2. Set kra1 as primary drm instance for TPS
3. Set external registration for kra2

Actual results:

TPS defaults to kra1 and recieves
"TPSSession.process: Message processing failed: TPSEnrollProcessor.enroll:
externalRegRecover: TPSEngine.recoverKey: Bad status from server: 9"

Expected results:

Key recovery succeeds.

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1439228

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1439228

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

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

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

Per CS/DS Meeting 09/25/2017: 10.5 blocker

Metadata Update from @mharmsen:
- Issue priority set to: blocker (was: major)

Metadata Update from @cfu:
- Issue assigned to cfu

commit aee9143177180a4d91d1dfff31f85f1da03b3141 (HEAD -> DOGTAG_10_4_BRANCH, 2631ExternalRegRecoverKRAfix10_4)
Author: Christina Fu cfu@redhat.com
Date: Mon Oct 2 09:22:58 2017 -0700

Ticket #2631 ExternalReg Recovery needs to go to the kra in user record
This patch fixes a bug in ExternalReg recovery where the kra connection info
is gotten from the profile instead of the user record certsToAdd field.
Change-Id: Ieacd75cc49452221e9719bcf8504869209217ce1

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

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

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.5.0-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/2751

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
None
None
None
Lowest
defect
''
''
Community
''
''
pki-core-10.5.0-1.fc27
General
''
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.