Currently the passwords for internal and replicationdb are randomly generated during installation. When Dogtag is started using nuxwdog, the admin will have to type in these passwords. Since randomly generated passwords are usually hard to memorize, the admin will have to save the passwords somewhere (e.g. file, post-it note), which defeats the purpose of using nuxwdog in the first place.
Option #1: pkispawn should be modified to use the same user-specified password as the internaldb for internal and replicationdb by default. This way the admin will only need to remember one password.
Option #2: pkispawn should accept user-specified passwords for internal and replicationdb. During startup the admin will still have to type in three passwords, but at least they will be easier to memorize.
Proposed milestone: 10.2.4
Per Dogtag 10.2.X TRIAGE meeting of 04/28/2015: 10.2.4
Fixed in master:
Metadata Update from @edewata:
- Issue assigned to edewata
- Issue set to the milestone: 10.2.4
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:
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.
to comment on this ticket.