Crypto (JCE)

JVM since1.1.0 Native since1.2.0

Sign and verify exchanges using the Signature Service of the Java Cryptographic Extension (JCE).

What’s inside

Please refer to the above links for usage and configuration details.

Maven coordinates

Create a new project with this extension on code.quarkus.io

Or add the coordinates to your existing project:

<dependency>
    <groupId>org.apache.camel.quarkus</groupId>
    <artifactId>camel-quarkus-crypto</artifactId>
</dependency>

Check the User guide for more information about writing Camel Quarkus applications.

Usage

Security Provider

Extension requires BouncyCastle provider and also utilizes the quarkus security extension (see security providers registration doc) If there is no BC* provider registered (by quarkus.security.security-providers property). The BC provider is registered.

FIPS

When running the crypto extension on FIPS enabled system any FIPS-compliant Java Security Provider (such as BCFIPS) has to be used.

  • In the case of BCFIPS, please add BCFIPS dependency and quarkus-security (see the guide for more information)

<dependency>
    <groupId>org.bouncycastle</groupId>
    <artifactId>bc-fips</artifactId>
</dependency>
<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-security</artifactId>
</dependency>

and register BCFIPS provider with following proprerty:

quarkus.security.security-providers=BCFIPS

  • Alternatively, you can add different FIPS compliant provider. Make Sure that the provider is registered.

Camel Quarkus limitations

SSL in native mode

This extension auto-enables SSL support in native mode. Hence you do not need to add quarkus.ssl.native=true to your application.properties yourself. See also Quarkus SSL guide.

Back to top