verify is an option in the man page. It is not explicit as to how to use the option. If it is not being used as intended, a better user experience would be to tell them why it is illegal. But at least, the man page needs to explain the usage properly.

Per CS/DS meeting of 08/25/2014: 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

This looks to be pretty straightforward. I have not verified this by checking code, but the most likely explanation (based on trial and error) is that "verify" is a usage that is valid for asymmetric keys only. So this is just a doc change.

Which means that the usage:

--usages Comma separated list of usages.
Valid values: wrap, unwrap, sign,
verify, encrypt, decrypt.
Additional usages for RSA and DSA type
keys: derive, sign_recover,
verify_recover.

should be:

--usages Comma separated list of usages.
Valid values: wrap, unwrap, sign,
encrypt, decrypt.
Additional usages for RSA and DSA type
keys: derive, sign_recover,
verify_recover, verify

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

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.