#645 Display the admin p12 file location in the installation summary
Closed: Fixed None Opened 9 years ago by kaskahn.

No Description Provided


Probably something like this:

============================
    INSTALLATION SUMMARY
============================

...
Client folder: /root/.dogtag/pki-tomcat/ca
...

============================

Tthe client folder will contain the certificate database folder, certificates, and p12 files. Some default paths may need to be modified.

Also, after your last change:

    ==========================================================================
                                INSTALLATION SUMMARY
    ==========================================================================

    Admin username: caadmin
    Client certificate nickname: PKI Administrator for example.com
    To check the status of the subsystem: 
        systemctl status pki-tomcatd\@pki-tomcat.service
    To restart the subsystem: 
        systemctl restart pki-tomcatd\@pki-tomcat.service
    The URL for the subsystem is https://pki.example.com:8443/ca

    ==========================================================================

For readability, please break the last line, add a ':', and indent the URL:

    ==========================================================================
                                INSTALLATION SUMMARY
    ==========================================================================

    Admin username: caadmin
    Client certificate nickname: PKI Administrator for example.com
    To check the status of the subsystem: 
        systemctl status pki-tomcatd\@pki-tomcat.service
    To restart the subsystem: 
        systemctl restart pki-tomcatd\@pki-tomcat.service
    The URL for the subsystem is:
        https://pki.example.com:8443/ca
    ==========================================================================

I think that the 'Admin username' and 'Client certificate nickname' can remain on a single line.

Fixed and pushed to master and 10_0_branch in 7e1a8b7f65170b154e917b6a65d20befc6bf7832 and edd2f6b5ee86f4b33c9c66c3efd5e217062dc80b respectively.

Metadata Update from @kaskahn:
- Issue assigned to kaskahn
- Issue set to the milestone: 10.0.4

5 years ago

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

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.

Login to comment on this ticket.

Metadata