The reactive REST client does not support P12, PEM and CRT/KEY files

[cescoffier]

Description

The reactive rest client only supports the JKS format at the moment. While this format is popular in the Java world, it's not popular (at all) anywhere else. CRT/KEY, PEM (the same as CRT/KEY), and P12 (PFX) are more popular.

Implementation ideas

The underlying HTTP client has support for these other formats, so this enhancement is about:

• adding the configuration key to pass the certificate and key files
• detect the format (based on the extension)
• configure the underlying client

Note that his work will enable the proper support of certificate reloading (it can be implemented with JKS, but most use case are about the other formats)

[quarkus-bot]

/cc @geoand (rest-client)

[winks]

Just stumbled over this and seeing geoand@7414953#diff-d374086457a41b4c533e9ff072d61977ce886022ded6173e358b6441b5f9c410R264 (I assume it's not merged and still being worked on) I just want to add that the quarkus reactive mailer seems to use "PKCS" as the truststore.type value and not PKCS12.

As I have no clue about quarkus internal consistency policies I'm just leaving this as a heads up here.

[geoand]

@cescoffier is working on a massive revamp of this

[cescoffier]

Yes, and the mailer is one of the components that will benefit from this large refactoring/ centralization.