Federico Mariani created CAMEL-27124:
----------------------------------------

             Summary: camel-spiffe - provide the workload JWT-SVID as a 
camel-oauth assertion, and keep the body on fetchJwtSvid
                 Key: CAMEL-27124
                 URL: https://issues.apache.org/jira/browse/CAMEL-27124
             Project: Camel
          Issue Type: Sub-task
          Components: camel-spiffe
            Reporter: Federico Mariani


Two additions so that camel-spiffe plugs into camel-oauth and HTTP calls 
without custom code:

* A bean {{org.apache.camel.component.spiffe.SpiffeJwtSvidAssertionProvider}} 
implementing the new {{OAuthAssertionProvider}} SPI: it fetches a JWT-SVID of 
the workload for the requested audience from the Workload API (options 
{{spiffeSocketPath}}, {{localSpiffeId}}). A camel-oauth profile uses it as 
client authentication (SPIFFE federated client authentication, no client 
secret), as the {{jwt-bearer}} grant of a workload identity federation (no API 
key), or as a bearer token for another workload.
{code}
camel.beans.spiffeJwt = 
#class:org.apache.camel.component.spiffe.SpiffeJwtSvidAssertionProvider
camel.oauth.idp.client-assertion-provider = #spiffeJwt
{code}
* {{fetchJwtSvid}} replaces the message body with the token, so the outbound 
call example of the documentation sends the token instead of its payload. With 
{{preserveBody=true}} (today only for {{validateJwtSvid}}), {{fetchJwtSvid}} 
sets the token in the {{CamelSpiffeToken}} header and keeps the body.

_Claude Code on behalf of Federico Mariani_




--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to