#450 CS 8.1 does not honor existing Subject Key Identifier
Closed: migrated 3 years ago by dmoluguw. Opened 11 years ago by nkinder.

https://bugzilla.redhat.com/show_bug.cgi?id=871185 (Red Hat Certificate System)

If certificate has an existing SKI, the CA does not honor it and re-calculates the SKI.

Steps to Reproduce:
1. Send request with pre-configured SKI to Dogtag CA for issuance.
2. Verify SKI after process

Actual results: SKI has been modified from initial request

Expected results: SKI should NOT be modified from initial request

If I recall correctly, this is actually for a special case where an existing CA signing cert wishes to have its existing CSR signed by our CA so that the previously established trust with its issued certs remains?
A good CA should probably not just take SKI straight from the CSR so we should be cautious not to open door to all requests.

proposed Milestone: 10.2.3 - Per Dogtag 10.2.3 meeting of 09/25/2014

Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2.2

Per 10.2.2 Triage meeting of 02/24/2015: 10.3

Metadata Update from @nkinder:
- Issue assigned to cfu
- Issue set to the milestone: UNTRIAGED

7 years ago

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

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 Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata