Currently there are two ways to specify the KRA connector hosts in the CA configuration file:
If there's only one host it has to be specified in the following properties:
ca.connector.KRA.host=kra.example.com ca.connector.KRA.port=8443
If there are multiple hosts, the host property turns into a list of hosts & ports, and the port property becomes unused:
ca.connector.KRA.host=kra1.example.com:8443 kra2.example.com:8443 ca.connector.KRA.port=8443
This mechanism is rather confusing and error prone, and the code has become unnecessarily complex since it has to handle multiple cases and the conversions between them.
To fix the problems, the KRA connector should use the same mechanism regardless of the number of hosts it has, for example:
ca.connector.KRA.hosts=kra1.example.com:8443,kra2.example.com:8443
or alternatively:
ca.connector.KRA.hosts.count=2 ca.connector.KRA.hosts.0.host=kra1.example.com ca.connector.KRA.hosts.0.port=8443 ca.connector.KRA.hosts.1.host=kra2.example.com ca.connector.KRA.hosts.1.port=8443
There should be an upgrade script to convert the existing CA configuration file.
Metadata Update from @edewata: - Issue set to the milestone: UNTRIAGED
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/2477
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.