[QPID-8402] [Broker-J][Tests] Use Bouncy Castle API to generate certificate resources on the fly in unit and system tests

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: qpid-java-broker-8.0.0
• Component/s: Broker-J
• Assignee: Alex Rudyy
• Reporter: Alex Rudyy
• Created: 22/Jan/20 10:35
• Updated: 12/Mar/20 20:20
• Resolved: 19/Feb/20 10:45

Description

Qpid Broker-J unit tests rely on a number of pre-generated kesstores, truststores, certificates, etc located either in module test resources folder or/and project folder ./test-profiles/test_resources/ssl. Those resources need to be regenerated periodically in order to keep them valid and up to date. As part of work at QPID-8367, the number of required test resources has increased.

A bash script was created in order to automate the generation, though, it seems, that a better approach would be to generate the required resources on runtime using Bouncy Castle API.

It is not exactly clear whether Bouncy Castle API would allow to generate all required test resources (including those added in QPID-8367). Though, we should switch to using Bouncy Castle API where it is possible, especially, for generation of self-signed certificates and test CA authority certificates and corresponding keystores/truststores.