oscerd commented on issue #1546:
URL:
https://github.com/apache/camel-kamelets/issues/1546#issuecomment-5573955833
Two questions here, and they have different answers.
## "Will kamelets add gRPC pub/sub support?"
Yes — #3012 adds `salesforce-pubsub-source`, which subscribes through the
gRPC Pub/Sub API rather than the older streaming API that `salesforce-source`
uses.
The component side has been ready for a while; the catalog simply had not
caught up. `camel-salesforce` in 4.22 carries both operations:
```
operationName enum -> [..., 'subscribe', 'pubSubSubscribe', 'pubSubPublish']
```
That PR covers `pubSubSubscribe`. A `pubSubPublish` sink is the obvious
companion and is a clean follow-up.
This overlaps #2263, which asks for the same thing. I have pointed the PR at
that one and left this open, because your second question is separate and still
unanswered.
## "Does the kamelet salesforce connector support keystores for
authentication?"
**No, and you were right that the parameters are not there.** Every
Salesforce Kamelet in the catalog builds its component bean with
username/password only:
```yaml
- name: local-salesforce
type:
"#class:org.apache.camel.component.salesforce.SalesforceComponent"
properties:
clientId: "{{clientId}}"
clientSecret: "{{clientSecret}}"
userName: "{{userName}}"
password: "{{password}}"
loginUrl: "{{loginUrl}}"
```
The component itself does support JWT bearer flow — `authenticationType`,
`jwtAudience` and `keystore` are all component options — so the gap is in the
Kamelets, not in Camel.
The awkward part is `keystore`: it is typed
`org.apache.camel.support.jsse.KeyStoreParameters`, an object rather than a
scalar. So exposing JWT auth means either building a `KeyStoreParameters` bean
inside each template from scalar properties, or accepting a bean reference from
the operator. That is the same shape as the decision in #3000 for the
OpenSearch Kamelets, and it would need applying consistently across all five
Salesforce Kamelets.
That is a real piece of work with a design choice in it rather than
something to fold into the Pub/Sub PR, so I have not attempted it here. If you
want it tracked properly it deserves its own issue — happy to write it up with
the options laid out.
---
_Claude Code on behalf of Andrea Cosentino_
--
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]
