#1125 Cert nickname should not be required with -c/-C.
Closed: Fixed Opened by edewata.

The -c/-C options are used to specify client security database password. Usually it's used for client cert authentication which also requires the cert nickname. The nickname can be specified with -n option. However, with client-init command the password is only used to create the client security database, it should not require a nickname. The code that requires -n when -C/-C is specified should be removed.

$ pki -c Secret123 client-init
Error:  If either of the '-C' or '-c' options are specified, the '-n' client authentication option must also be specified!

Proposed milestone: 10.2


The 'pki' man page should also be updated when this is fixed, as it currently states that -n is required with -c/-C:

       -c <client security database password>
              Specifies the client security database password (mutually exclusive to the '-C' option; requires the '-n' client authentication option).
       -C <client-side password file>
              Specifies the file which contains the client security database password (mutually exclusive to the '-c' option;  requires  the  '-n'  client
              authentication option).

Moved to 10.2.1.

master: 2f7e6de6c489a49f7a7be473e5752ef49472bbcc

Metadata Update from @edewata:
- Issue assigned to edewata
- 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/1688

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