davsclaus opened a new issue, #3242:
URL: https://github.com/apache/camel-kamelets/issues/3242

   Some Kamelets put a password, key or other credential option into the 
address of the endpoint they call without wrapping it in `RAW()`. The address 
is then parsed as a URI, so a value with a character such as `&`, `+` or `=` is 
cut into another parameter or changed: a password `p&ss+w=rd` logs in as `p`, 
and with the HTTP Kamelets the rest of it is added to the query of the request. 
A Base64 service account key with a `+` in it is changed the same way. Wrapping 
the value in `RAW()` in the route that uses the Kamelet does not help, because 
the Kamelet places the value into its own address.
   
   Change: every option with `format: password` that goes into an endpoint 
address, as a URI query parameter or as an entry of `parameters`, is wrapped in 
`RAW()`, as most Kamelets already do. This affects about 30 Kamelets, among 
them `http-sink` and `http-source` (`authPassword`, `oauth2ClientId`, 
`oauth2ClientSecret`), `mail-sink`, `cassandra-sink`, 
`infinispan-sink`/`-source`, the Google Kamelets (`serviceAccountKey`, 
`clientId`), the Azure Storage Kamelets (`tenantId`, `clientId`), the Kafka 
Apicurio Kamelets, `nats-sink`/`-source` (`servers`), `slack-sink` 
(`webhookUrl`) and `ceph-event-based-source`.
   
   A test in the catalog checks every Kamelet, so a new option with `format: 
password` in an address without `RAW()` fails the build.
   
   _Claude Code on behalf of Claus Ibsen_
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to