Currently KRA supports the following types for key archival:
The type is used by KRA to categorize the keys and/or perform the appropriate key validations.
However, KRA is now being used to archive more generic data, not just keys. So if the data to be archived is arbitrary binaries, or unknown, or if no validations is wanted, the only type that can be used now is PASS_PHRASE_TYPE. This type may not be appropriate because the name implies that it's a text data, and there's no indication that there won't be any validations performed against it.
A possible solution is to add a new BLOB_TYPE or UNKNOWN_TYPE, or replace PASS_PHRASE_TYPE with it.
There is nothing wrong with the functionality. It's just the current options are not very developer-friendly.
Per Dogtag 10.2.3 Triage meeting of 09/24/2014 - proposed Milestone: 10.2.1
NOTE: This may simply require documentation rather than any code changes.
After discussion with vakwetu on 12/12/2014, it was determined that this ticket could be moved to 10.2.2.
Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2 Backlog
Per 10.2.3 TRIAGE meeting of 02/26/2015: 10.3
NOTE: Moved from 10.2 Backlog since it was not a documentation/man page issue.
Metadata Update from @edewata: - 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/1717
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)