PQC Algorithms

Post Quantum Cryptography Signature and Verification component.

Metadata

Property	Value
Scheme	`pqc`
Support Level	Stable
Labels	security
Version	4.20.0 (CEQ 3.36.0)

Maven Dependency

<dependency>
    <groupId>org.apache.camel.quarkus</groupId>
    <artifactId>camel-quarkus-pqc</artifactId>
    <version>4.20.0 (CEQ 3.36.0)</version>
</dependency>

Endpoint Properties

Name	Type	Required	Default	Description
`label`	string	✓		Logical name
`operation`	enum	✓		The operation to perform
`lazyStartProducer`	boolean		`false`	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.
`classicalKEMAlgorithm`	enum			The classical key agreement algorithm to use in hybrid KEM operations
`classicalKeyAgreement`	object			The classical KeyAgreement instance to be used in hybrid KEM operations
`classicalKeyPair`	object			The classical KeyPair to be used in hybrid operations
`classicalSignatureAlgorithm`	enum			The classical signature algorithm to use in hybrid operations
`classicalSigner`	object			The classical Signature instance to be used in hybrid signature operations
`hybridKdfAlgorithm`	enum		`HKDF-SHA256`	The KDF algorithm to use for combining secrets in hybrid KEM operations
`keyEncapsulationAlgorithm`	enum			In case there is no keyGenerator, we specify an algorithm to build the KeyGenerator
`keyGenerator`	object			The Key Generator to be used in encapsulation and extraction
`keyLifecycleManager`	object			The KeyLifecycleManager to use for key lifecycle operations such as generation, rotation, import/export, expiration, and revocation
`keyPair`	object			The KeyPair to be used
`keyPairAlias`	string			A KeyPair alias to use in combination with KeyStore parameter
`keyStore`	object			A KeyStore where we could get Cryptographic material
`keyStorePassword`	string			The KeyStore password to use in combination with KeyStore Parameter
`signatureAlgorithm`	enum			In case there is no signer, we specify an algorithm to build the KeyPair or the Signer
`signer`	object			The Signer to be used
`statefulKeyWarningThreshold`	number		`0.1`	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.
`storeExtractedSecretKeyAsHeader`	boolean		`false`	In the context of extractSecretKeyFromEncapsulation operation, this option define if we want to have the key set as header
`strictKeyLifecycle`	boolean		`true`	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.
`symmetricKeyAlgorithm`	enum			In case we are using KEM operations, we need a Symmetric algorithm to be defined for the flow to work.
`symmetricKeyLength`	integer		`128`	The required length of the symmetric key used