Andrea Cosentino created CAMEL-26833:
----------------------------------------
Summary: camel-spiffe - expose identity readiness, expiry and
refresh status
Key: CAMEL-26833
URL: https://issues.apache.org/jira/browse/CAMEL-26833
Project: Camel
Issue Type: Improvement
Components: camel-spiffe
Reporter: Andrea Cosentino
Assignee: Andrea Cosentino
h2. Problem / motivation
SPIFFE has no component-specific readiness implementation comparable to
OPA/OpenFGA. Operators need to distinguish usable cached identity from
missing/expired material and temporary Workload API disconnection.
h2. Proposed scope
Add bounded readiness and identity status covering SVID availability, remaining
validity, configured expiry threshold, last successful refresh and source
connection state. Reuse managed source state where possible and avoid a
credential fetch for every health request.
h2. Acceptance criteria / validation
* Test no identity, valid identity, approaching expiry, expiry and
disconnect/reconnect with still-valid cached material.
* Expose no tokens, keys or certificate contents by default.
* Verify registration/removal on lifecycle changes and document readiness
semantics.
h2. References
*
https://github.com/apache/camel/blob/5686684cb418/components/camel-spiffe/src/main/java/org/apache/camel/component/spiffe/SpiffeEndpoint.java
*
https://github.com/apache/camel/blob/5686684cb418/components/camel-spiffe/src/main/java/org/apache/camel/component/spiffe/SpiffeSSLContextParameters.java
Source: read-only component audit at 5686684cb418. Recheck current main before
implementing; historical references identify the audited code.
_AI-generated by Codex on behalf of oscerd (JIRA: acosentino)._
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
