CA's CS.cfg doesn't pick right port even if we provide different ports in pkispawn file.for example:
pkispawn file has:
pki_https_port=23443 pki_http_port=23080
CS.cfg file has:
http.port=8080 https.port=8443 ca.Policy.rule.AuthInfoAccessExt.ad0_location=http://pki1.example.com:8080/ocsp
Actual results:
Port in CS.cfg of CA still shows the default ones.
Expected results:
New ports should get updated.
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1452123 - Custom field type adjusted to defect - Custom field version adjusted to ''
Metadata Update from @mharmsen: - Issue assigned to mharmsen
Metadata Update from @mharmsen: - Issue priority set to: critical
commit e1fd9685e5442e5e2efa9a26e07bf45274b6fb93 Author: Matthew Harmsen mharmsen@redhat.com Date: Fri May 19 09:47:47 2017 -0600
Fixed hardcoded values in ca CS.cfg - Bugzilla Bug #1452123 - CA CS.cfg shows default port - dogtagpki Pagure Issue #2696 - CA CS.cfg shows default port
Metadata Update from @mharmsen: - Issue close_status updated to: fixed - Issue set to the milestone: 10.4.5 (was: 10.4) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.4.7-1.fc27
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/2816
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.