TLS: Introduce key-store-key-password

[famod]

The ability to set such a key-specific password was added to vert.x 4.1.1 via eclipse-vertx/vert.x#3970 / eclipse-vertx/vert.x#3982

See also #17884 which added the alias.

The only change to server-keystore.jks is "serverpw" instead of "password" for the entry with name "server".

[famod]

@geoand @michalszynkiewicz I think both alias and password could be interesting for the RR client (ClientBuilderImpl, AFAICS).

The same might apply to VertxSpringCloudConfigGateway, GrpcSslUtils and VertxConsulConfigGateway as well.

[quarkus-bot]

Failing Jobs - Building fa325a3

Status	Name	Step	Test failures	Logs	Raw logs
✖	MicroProfile TCKs Tests	Verify	Test failures	Logs	Raw logs

Full information is available in the Build summary check run.

Test Failures

⚙️ MicroProfile TCKs Tests #

📦 tcks/microprofile-fault-tolerance

✖ org.eclipse.microprofile.fault.tolerance.tck.TimeoutUninterruptableTest.testTimeoutAsyncBulkhead line 190 - More details - Source on GitHub

[geoand]

@geoand @michalszynkiewicz I think both alias and password could be interesting for the RR client (ClientBuilderImpl, AFAICS).

The same might apply to VertxSpringCloudConfigGateway, GrpcSslUtils and VertxConsulConfigGateway as well.

Yeah, I think we've discussed similar things in the past :)

[famod]

@cescoffier it seems you are ok with the PR as is? If yes, can you approve please?
Please let me know if there is anything left to look into. Thanks!

/cc @sberyozkin in case you are want to have a look as well...

[cescoffier]

@famod Yes, let me update my review.

[famod]

That one FT test failure looks flaky to me:

Bulkhead[org.eclipse.microprofile.fault.tolerance.tck.timeout.clientserver.UninterruptableTimeoutClient#serviceTimeoutAsyncBulkhead] rejected from bulkhead

/cc @Ladicek

[sberyozkin]

LGTM, thanks

[famod]

Thanks all!

[Ladicek]

@famod Yes, TimeoutUninterruptableTest.testTimeoutAsyncBulkhead is flaky (see also smallrye/smallrye-fault-tolerance#233). It doesn't fail often, and I didn't see it failing locally or in SmallRye Fault Tolerance CI, so I've neglected investigating it. Sorry about that! :-)