We created a user (pkidbuser) to be able to connect to the database using client certificate authentication.
The problem is that we chose to use the subsystem certificate for this user, rather than creating a new system cert for db interactions. There is, however, another user that has been created for the CA-DS interaction which has the same certificate. This user is in the trusted manager's group.
So, in this case, when the CA connects to the KRA and presents the subsystem cert, we retrieve the wrong user (pkidbuser, which is not in the Trusted Users group) - and the KRA-CA connector fails.
The simplest solution was to add the pkidbuser to the Trusted Managers group, which was done in PKI TRAC Ticket #1595 - CA fails to authenticate to KRA for archival to address this issue.
However, this still leaves the problem that there are two "users" that share the same cert and could create maintenance confusion.
This ticket was filed to resolve this issue.
Metadata Update from @mharmsen: - Issue set to the milestone: 10.4
Per CS/DS meeting of 04/24/2017, it was discussed and believed that this ticket could wait until after 10.4, so moving to 10.5.
Metadata Update from @mharmsen: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None - Issue set to the milestone: 10.5 (was: 10.4)
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/2155
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.