pkispawn of TPS is successful when CA's secure http port is assigned as TPS' unsecure http port

[pki-bot]

This issue was migrated from Pagure Issue #1560. Originally filed by rpattath (@rpattath) on 2015-08-13 23:50:30:

• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1253453

---

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

[pki-bot]

Comment from mharmsen (@mharmsen) at 2015-08-18 01:37:26

Per CS/DS Meeting of 08/17/2015 - 10.3

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-05-06 22:14:30

Per Bug Triage of 05/05/2016: 10.4

NOTE: make this a self-test check.

[pki-bot]

Comment from rpattath (@rpattath) at 2017-02-27 14:12:15

Metadata Update from @rpattath:

• Issue set to the milestone: UNTRIAGED

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-08-30 22:41:47

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)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-04-13 18:40:47

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