Currently the CLI takes a -w <password> option to specify the password which is not secure because it will be logged in shell history. The password is used to login to the server or to access the certificate database.
There other ways to specify the password:
Prompting for password. This is the simplest to use, but it may not work for automation.
Using a password file. This file could also contain connection info so these parameters do not need to be repeated in every CLI invocations. User is responsible to remove it afterwards.
Although it is hoped that this ticket will be started in June (after the RHEL 6 work), it most likely will not be finished until July, so moving the ticket to the 10.2 (July) milestone.
currently out for review
Checked into 'master':
Metadata Update from @edewata: - Issue assigned to mharmsen - 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/1125
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.
Login to comment on this ticket.