Provide shared secret storage and retrieval and associated mechanism that can be utilized in areas such as CMC id-cmc-identityProofV2.
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1428021
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: 2 - Issue set to the milestone: 10.4 (was: 0.0 NEEDS_TRIAGE)
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 76eca860d5d87b78156d1478306e8efab0c2c9e1 (HEAD -> master, origin/master, origin/HEAD) Author: Christina Fu cfu@redhat.com Date: Wed Oct 18 14:27:03 2017 -0700
Ticket #2604 RFE: shared token storage and retrieval mechanism This patch provides the implementation for the SharedSecret class that implements the SharedToken interface to support CMC enrollment and revocation based on shared secret between client and server. This patch also contains a new tool, CMCSharedToken that can be used to take a passphrase as input and produce the secret data that is to go into its respective ldap entry. The secret data takes on the following format that has been long adopted by the KRA key/secret archival features: SEQUENCE { encryptedSession OCTET STRING, encryptedPrivate OCTET STRING } See design at: https://pki.fedoraproject.org/wiki/PKI_10.5_CMC_Shared_Token Additionally, this patch also addressed the ReqID inconsistency issue in the CMC revocation area in CMCOutputTemplate.java Change-Id: I1bbf34d9d30e7fe43b89bfb6e1b471756f2d649b
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: - Issue set to the milestone: 10.5.1 (was: 10.5.0)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.5.1-1.fc27
Originally fixed in 'pki-core-10.5.1-1.fc27'; re-opened due to testing anomoly.
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.5.1) - Issue status updated to: Open (was: Closed)
commit e66cf40df2cf647ca220f95417d3b3382d7e8381 (HEAD -> master, origin/master, origin/HEAD, cmcFIPS) Author: Christina Fu cfu@redhat.com Date: Wed Dec 20 14:08:58 2017 -0800
Ticket #2604 adding FIPS support-RFE: shared token storage and retrieval mechanism This patch adds FIPS support to the original ticket 2604. Two changes were made: 1. in CMCSharedToken tool, "-p" is used to specify the password for token login and "-s" is used to specify the shared secret (or passphrase) 2. on the server side, in SharedSecret, an existing configuration parameter, cmc.token is utilized for admin to specify the token where the issuance protection cert's private key resides on. Change-Id: Ia454598bca7843bfc0a6ad21f57f6a74d05d67fe
Metadata Update from @cfu: - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue close_status updated to: fixed - Issue set to the milestone: 10.5.4 (was: 10.5)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.5.4-1.fc27 (was: pki-core-10.5.1-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/2724
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.