[
https://issues.apache.org/jira/browse/CAMEL-22860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053256#comment-18053256
]
Bhagyashree Ambavane commented on CAMEL-22860:
----------------------------------------------
Hello Camel team,
This issue is causing functional impact in our production usage of Apache
Camel. We kindly request if this bug can be prioritized and added to a
forthcoming sprint.
We are available to assist with reproducer steps, logs, or verification to help
move this forward.
Thank you for your time and support!
Regards,
Bhagyashree
> Camel-Salesforce - Pub/Sub API reconnect attempts causing infinite
> re-subscribe loop
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-22860
> URL: https://issues.apache.org/jira/browse/CAMEL-22860
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
> Affects Versions: 4.8.0, 4.8.2, 4.14.3, 4.16.0, 4.17.0
> Reporter: Bhagyashree Ambavane
> Priority: Major
> Attachments: Exception Details.txt
>
>
> When subscribing to multiple Salesforce Platform Events via the Pub/Sub API
> using the OAuth 2.0 JWT Bearer Flow, the Camel client enters a continuous
> re‑subscription loop. This prevents stable long‑lived event consumption.
> Authentication method: OAuth 2.0 JWT Bearer Flow.
> *Steps to Reproduce*
> Configure Camel Salesforce component with JWT bearer flow credentials.
> Subscribe to multiple Platform Events using the Pub/Sub API.
> Observe client behavior during re‑subscription attempts.
> *Observed Behavior*
> Initial subscription succeeds.
> Client attempts to re‑subscribe.
> Subscription fails due to some error.
> Instead of refreshing the JWT token, the client retries indefinitely,
> resulting in a loop of failed re‑subscriptions.
> *Impact*
> Subscriptions become unstable after re-subscription attempt.
> *Technical Notes*
> The issue appears to be related to token lifecycle management in the Camel
> Salesforce component.
> The JWT bearer flow does not support refresh tokens; instead, a new JWT
> assertion must be exchanged for a fresh access token.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
