PQC Algorithms

Component configuration.

Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.

Required The operation to perform.

Enum values:

Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.

The classical key agreement algorithm to use in hybrid KEM operations.

Enum values:

Autowired The classical KeyAgreement instance to be used in hybrid KEM operations.

Autowired The classical KeyPair to be used in hybrid operations.

The classical signature algorithm to use in hybrid operations.

Enum values:

Autowired The classical Signature instance to be used in hybrid signature operations.

The KDF algorithm to use for combining secrets in hybrid KEM operations.

Enum values:

In case there is no keyGenerator, we specify an algorithm to build the KeyGenerator.

Enum values:

Autowired The Key Generator to be used in encapsulation and extraction.

Autowired The KeyLifecycleManager to use for key lifecycle operations such as generation, rotation, import/export, expiration, and revocation.

Autowired The KeyPair to be used.

A KeyPair alias to use in combination with KeyStore parameter.

Interval between key rotation checks when the scheduler is enabled.

When the scheduler is enabled, rotate keys older than this age. If not set, age is not used as a rotation signal.

When the scheduler is enabled, rotate keys whose recorded usage count reaches this value. 0 disables usage-based rotation.

Whether to start an automated background key rotation scheduler for this component. Requires keyLifecycleManager to be set. The scheduler periodically rotates keys that exceed the configured age and/or usage policy.

Autowired A KeyStore where we could get Cryptographic material.

The KeyStore password to use in combination with KeyStore Parameter.

The NIST parameter set (security level) to use for the configured signature or key encapsulation algorithm, using the BouncyCastle parameter-set names: for example ML-DSA-44, ML-DSA-65 or ML-DSA-87 for MLDSA, and ML-KEM-512, ML-KEM-768 or ML-KEM-1024 for MLKEM. Names are case-insensitive and the underscore form (ml_dsa_87) is accepted as an alias. When set, the key material is generated with this parameter set instead of the algorithm default. Not supported for the stateful signature algorithms (XMSS, XMSSMT, LMS, HSS), for MAYO and SNOVA, nor for the hybrid operations: for those, register a KeyPair bean in the registry instead.

In case there is no signer, we specify an algorithm to build the KeyPair or the Signer.

Enum values:

Autowired The Signer to be used.

The warning threshold for stateful key exhaustion as a fraction of total signatures (0.0 to 1.0). When the remaining signatures for a stateful key (XMSS, XMSSMT, LMS/HSS) drop below this fraction of the total capacity, a WARN log is emitted. When remaining signatures reach zero, an exception is thrown to prevent key reuse. Set to 0 to disable warnings.

In the context of extractSecretKeyFromEncapsulation operation, this option define if we want to have the key set as header.

Whether to enforce key status checks before cryptographic operations. When enabled, REVOKED keys are rejected for all operations, EXPIRED keys are rejected for signing/encapsulation but allowed for verification/extraction, and DEPRECATED keys produce a warning but still function. Requires a KeyLifecycleManager and a CamelPQCKeyId header to be set.

In case we are using KEM operations, we need a Symmetric algorithm to be defined for the flow to work.

Enum values:

The required length of the symmetric key used.

Used for enabling or disabling all consumer based health checks from this component.

Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true.

The operation we want to perform.

The signature of a body.

The result of verification of a Body signature.

The extracted key in case of extractSecretKeyFromEncapsulation operation and storeExtractedSecretKeyAsHeader option enabled.

The remaining signatures for a stateful key.

The key state for a stateful key.

The key ID for stateful key operations.

The generated key pair.

The key format for import/export operations.

The exported key data.

The key metadata.

List of key metadata.

The algorithm for key generation.

Include private key in export.

Revocation reason.

The hybrid signature combining both classical and PQC signatures.

The classical signature component of a hybrid signature.

The PQC signature component of a hybrid signature.

The classical encapsulation component of a hybrid KEM.

The PQC encapsulation component of a hybrid KEM.

The combined secret key from hybrid KEM operation.

The hybrid encapsulation combining both classical and PQC encapsulations.

The verification result of hybrid signature (both must pass).