[
https://issues.apache.org/jira/browse/CAMEL-22512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18097032#comment-18097032
]
Andrea Cosentino commented on CAMEL-22512:
------------------------------------------
The key lifecycle management feature was implemented via
https://github.com/apache/camel/pull/19494 (KeyLifecycleManager with in-memory
and file-based implementations), released in 4.16.0, with follow-ups
CAMEL-22522 (HashiCorp Vault), CAMEL-22528 (AWS Secrets Manager) and
CAMEL-23098 (producer wiring). Closing as Fixed for 4.16.0; the remaining Azure
Key Vault manager is tracked separately in CAMEL-22538.
_Claude Code on behalf of Andrea Cosentino (@oscerd)._
> Camel-PQC: Add Key Lifecycle Management
> ----------------------------------------
>
> Key: CAMEL-22512
> URL: https://issues.apache.org/jira/browse/CAMEL-22512
> Project: Camel
> Issue Type: New Feature
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.16.0
>
>
> Add key lifecycle management capabilities to the camel-pqc component for
> managing Post-Quantum Cryptography keys throughout their entire lifecycle.
> In the beginning we could save the Key state in memory (for development) or
> on File. Then we could choose to move on something more enterprise like for
> example CloudKMSKeyLifecycleManager or VaultKeyLifecycleManager
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
