Thanks to @Otavio Rodolfo Piske suggestion of setting the api version
higher than 34 (in my case I set it to 48) and it works fine now.
Thanks Otavio! After setting the API to 48 I can now receive the Event.
On Thu, May 21, 2020 at 8:29 PM Otavio Rodolfo Piske
wrote:
>
> Hello,
>
> I think it might be related to the Salesforce API version. Camel uses 34.0
> by default and I think you need, at least, 37.0. I noticed a similar
> co
Yes, that’s quite clear. I wonder if there is an access to the OSGi CLI
commands jaas:* from a Camel route directly. At the moment I‘m using camel-exec
with the karaf client.
Sent by my mobile device
- Gerald Kallas
> Am 21.05.2020 um 19:42 schrieb Alex Soto :
>
> One way to do this is to sto
One way to do this is to store the user and role directly in the underlying
storage for the JAAS security context.
For example, in the case of the default “karaf” security context, users and
roles are stored in the ‘etc/users.properties’ file, but you may choose to
store this in a database tabl
Hello,
I think it might be related to the Salesforce API version. Camel uses 34.0
by default and I think you need, at least, 37.0. I noticed a similar
condition when working on the Salesforce test cases for the Camel Kafka
Connector.
I am quoting below the comment I added to the test case as to w
