TLS: Introduce *-alias to select specific key to use (or cert to trust)

[famod]

Resolves #17424

Notes on store modifications in integration-tests/vertx-http:

• added key pair to server-keystore.jks with alias "anotherserver" (which comes before the existing "server" pair)
• added key pair to new client-keystore-2.jks and added its cert chain to server-truststore.jks with alias "mykey-2"
• renamed existing "mykey" to "mykey-1" in server-truststore.jks
• renamed client-keystore.jks to client-keystore-1.jks

---

More notes:

• I unified the creation of KeyStoreOptions in the recorder
• I went with the parameter naming suggestion but maybe those names are a bit misleading because those are aliases for entries in stores, not aliases of stores, but then again I might be splitting hairs here

[quarkus-bot]

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building 68bedec

Status	Name	Step	Test failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 16	Build	Test failures	Logs	Raw logs

Full information is available in the Build summary check run.

Test Failures

⚙️ JVM Tests - JDK 16 #

📦 extensions/vertx-http/deployment

✖ io.quarkus.vertx.http.testrunner.TestChangeTrackingWhenStartFailsTestCase.testChangeTrackingOnStartupFailure line 42 - More details - Source on GitHub

[famod]

I had a talk with my colleague @mickroll and I think this parameter naming question becomes more relevant:
In JBoss/WildFly, Spring Boot etc. you can also specify a password for the key (not the store!) and I'm planning on requesting this in vert.x (and adding it to Quarkus once it has been released).
This would lead to a conflict with key-store-password if key-store-alias stays like this.

Maybe it would be better to have:

• key-store-key-alias
• key-store-key-password

?
Or even a "sub-section":

• key-store-key.alias
• key-store-key.password

?
Another approach would be to not use key-store- prefix at all for this...

WDYT?

[sberyozkin]

@famod

    key-store-key-alias
    key-store-key-password

are definitely better, and for this PR in particular, key-store-key-alias as it is exactly what it is, thanks

[famod]

Remarks have been addressed. Btw, I went with trust-store-cert-alias for the trust store param.

[quarkus-bot]

This workflow status is outdated as a new workflow run has been triggered.

🚫 This workflow run has been cancelled.

Failing Jobs - Building c06b35d

⚠️ Artifacts of the workflow run were not available thus the report misses some details.

Status	Name	Step	Test failures	Logs	Raw logs
⌛	Initial JDK 11 Build	Build	⚠️ Check →	Logs	Raw logs

[quarkus-bot]

Failing Jobs - Building 0f68fa1

Status	Name	Step	Test failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 11 Windows	Build	Test failures	Logs	Raw logs
✔️	JVM Tests - JDK 16

Full information is available in the Build summary check run.

Test Failures

⚙️ JVM Tests - JDK 11 Windows #

📦 integration-tests/resteasy-reactive-rest-client

✖ io.quarkus.it.rest.client.BasicTest.shouldMakeJsonRequest line 40 - More details - Source on GitHub

[sberyozkin]

Looks it is OK to merge, Clement @cescoffier has also approved, the failing test on Windows is not related to this PR