dogtagpki

#394 Feature: Support multiple Subject Key Identifier generation methods
Closed: migrated by dmoluguw. Opened by cfu.

Closed: migrated
Reopen Issue

This is in response to the customer Salesforce ID 00728279. Bug 871185 - CS 8.1 does not honor existing Subject Key Identifier https://bugzilla.redhat.com/show_bug.cgi?id=871185

Currently our CS (RHCS, Dogtag) supports only one single method, which is per RFC 5280 (3280 etc.)
"composed of the 160-bit SHA-1 hash of the
value of the BIT STRING subjectPublicKey (excluding the tag,
length, and number of unused bits)"

We need to allow different methods.

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

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

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)
Metadata
None
None
None
Normal
enhancement
CA
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.