Currently the pkispawn man page provides an instruction to setup TLS using setupssl2.sh. Since this script is not part of officially released product the instruction should be replaced with a step-by-step instruction as described in the following page:
http://pki.fedoraproject.org/wiki/Enabling_SSL_Connection_with_Internal_Database
The man page should mention something like "refer to the 389 DS documentation for details on configuring TLS."
http://directory.fedoraproject.org/docs/389ds/howto/howto-ssl.html
rpattath wrote:
man page should not point to a script on github for enabling ssl on ldap (https://raw.githubusercontent.com/richm/scripts/master/setupssl2.sh).
Either the steps to enable ssl on ldap should be described or point to 389 DS documentation.
Per PKI Bug Council of 06/23/2016: 10.3.4
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 @edewata: - 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 priority set to: critical (was: major)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.4)
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/2476
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.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.