pkispawn of TPS is successful when CA's secure http port is assigned as TPS' unsecure http port
Steps to Reproduce:
1. pkispawn CA with secure http port 30042 2. pkispawn KRA and TKS 3. pkispawn TPS with 30042 as the unsecure http port
Actual results:
pkispawn is successful but unable to perform token format/enroll operations with the unsecure port
Expected results:
pkispawn should complain
Additional info:
Created attachment 1062736 in associated bug TPS debug log
Per CS/DS Meeting of 08/17/2015 - 10.3
Per Bug Triage of 05/05/2016: 10.4
NOTE: make this a self-test check.
Metadata Update from @rpattath: - Issue set to the milestone: UNTRIAGED
Metadata Update from @mharmsen: - Custom field feature adjusted to None - Custom field lowhangingfruit adjusted to vakwetu: X - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: None - Issue set to the milestone: FUTURE (was: UNTRIAGED)
Per 10.5.x/10.6 Triage: FUTURE
mharmsen: problem occurs when a configuration issue is made; while it should be looked at, since the TPS instance configures but does not work it seems like a minor issue
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/2119
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.