#2376 [MAN] pki-client manpage needs info about client-cert-validate command
Closed: migrated by dmoluguw. Opened by nkinder.

The 'client-cert-validate' subcommand was added to the 'pki' CLI in Dogtag 10.3.x. The 'pki-client' man page still needs to be updated to describe how to use this command.

We need to make sure to include details on the format of the --certusage option, as it's unclear what is expected from the usage message:

 usage: client-cert-validate nickname
    --certusage <certusage>   Certificate usage.
    --help                    Show help options

Based on the code the following usages are supported:

  • !CheckAllUsages
  • SSLServer
  • SSLServerWithStepUp
  • SSLClient
  • SSLCA
  • AnyCA
  • !StatusResponder
  • !ObjectSigner
  • !UserCertImport
  • !ProtectedObjectSigner
  • VerifyCA
  • !EmailSigner

The following usage probably should have been supported as well, but it's missing from the code:

  • !EmailRecipient

If no usage is specified, the command will show the usages that the certificate supports.

Per PKI Bug Council of 06/23/2016: 10.3.4

In ticket #2399 the CLI help message has been modified to list the supported usages. Also the missing EmailRecipient has been added.

See also: http://pki.fedoraproject.org/wiki/Certificate_Usages

Per CS/DS Meeting of 08/08/2016: 10.3.6

Per PKI Bug Council of 02/09/2017: 10.3 => 10.4

Metadata Update from @nkinder:
- Issue set to the milestone: 10.4

Metadata Update from @mharmsen:
- Custom field feature adjusted to ''
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field version adjusted to ''
- Issue close_status updated to: None
- Issue set to the milestone: 10.5 (was: 10.4)

Metadata Update from @mharmsen:
- Issue priority set to: critical (was: major)

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

[20171025] - Offline Triage ==> 10.6

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: 10.5)

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

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.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

Metadata