The term "Client ID" was changed some time ago to "Client Key ID" to avoid confusion between "an ID identifying the client" and "a client-defined ID for the key". Some CLI still use "Client ID" in the output and help messages:
[root@vm-084 scripts]# pki ... key-find ---------------- 1 key(s) matched ---------------- Key ID: 0x1 Client ID: test Status: active Algorithm: RSA Size: 1024 Owner: kraadmin ---------------------------- Number of entries returned 1 ---------------------------- [root@vm-084 scripts]# pki key-find --help usage: key-find [OPTIONS...] --client <client ID> Client ID --help Show help options --maxResults <max results> Maximum results --maxTime <max time> Maximum time --size <size> Page size --start <start> Page start --status <status> Status [root@vm-084 scripts]# pki ... key-archive Error: Client Key Id is not specified. usage: key-archive [OPTIONS...] --clientKeyID <Client Key Identifier> Unique client key identifier. --help Show help options --input <Input file path> Location of the request template file. Used for archiving already encrypted data. --passphrase <Passphrase> Passphrase to be stored.
Proposed milestone: 10.2 August
Fixed and pushed to master in a7f8076a5f20812eceac31f7230e4156adf74471
Metadata Update from @edewata: - Issue assigned to kaskahn - Issue set to the milestone: 10.2 - 08/14 (August)
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/1653
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.