In the pki key archival, we have an option to pass --input , where we pass an xml file to archive a key. Man page of pki-key specifies the below template to be used for pki key archival.
-- clientKeyID - Unique identifier for the secret. -- dataType - Type of the data to be stored which can be passphrase/symmetricKey/asymmetricKey. -- keyAlgorithm - Algorithm used to create a symmetric key. (Not required if the dataType is passphrase) -- keySize - Size used to generate the symmetric key. (Not required if the dataType is passphrase) -- algorithmOID - Key Algorithm object identifier -- symmetricAlgorithmParams - Base64 encoded nonce data. Nonce used while encrypting the secret. -- wrappedPrivateData - Secret encrypted using a session key(A symmetric key) encoded using Base64. This entity contains the secret which is encrypted using a session key. -- transWrappedSessionKey - The session key used to encrypt the secret, wrapped using the DRM transport key, and encoded in Base64 format. -- pkiArchiveOptions - An object of type PKIArchiveOptions provided by the NSS/JSS library to securely transport a secret encoded in Base64 format.
How to generate an object of type "pkiArchiveOptions".
Man page doesn't specify how the pkiArchiveOptions be generated.
Per CS/DS meeting of 12/05/2014: Milestone 10.2.3
Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2 Backlog
As this ticket relates to a man page, no specific Bugzilla Bug is required.
Per PKI Bug Council of 06/23/2016: 10.3.4
edewata asked to re-assign this to vakwetu and mark it major
Metadata Update from @mrniranjan: - 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/1787
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.