Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simplifying KRA connector configuration #2477

Open
pki-bot opened this issue Oct 3, 2020 · 1 comment
Open

Simplifying KRA connector configuration #2477

pki-bot opened this issue Oct 3, 2020 · 1 comment
Milestone

Comments

@pki-bot
Copy link

pki-bot commented Oct 3, 2020

This issue was migrated from Pagure Issue #2357. Originally filed by edewata (@edewata) on 2016-06-13 20:27:23:

  • Assigned to nobody

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.

@pki-bot pki-bot added this to the UNTRIAGED milestone Oct 3, 2020
@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from edewata (@edewata) at 2017-02-27 14:01:57

Metadata Update from @edewata:

  • Issue set to the milestone: UNTRIAGED

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant