Serge Huber created UNOMI-989:
---------------------------------
Summary: Upgrade the Salesforce connector
Key: UNOMI-989
URL: https://issues.apache.org/jira/browse/UNOMI-989
Project: Apache Unomi
Issue Type: Improvement
Reporter: Serge Huber
Fix For: unomi-3.2.0
h3. Summary
The Salesforce connector has not been updated for a long time. It still uses an
old Salesforce API version and an older way to log in. Salesforce is moving to
newer login methods and API versions, so this connector needs a refresh to stay
usable.
The goal of this ticket is to bring the Salesforce connector up to date: use
current Salesforce login and API practices, and update the libraries it embeds
for streaming (CometD and its Jetty HTTP client). Those libraries live only
inside this extension, so they can be upgraded without changing the Jetty
version used by the rest of Unomi.
A Dependabot pull request only bumps CometD to a new major version. That is not
enough on its own and should wait for this wider upgrade.
h3. Ways to explore
* Review which Salesforce login methods are recommended for server-to-server
use today, and switch the connector to one of them.
* Move the REST and streaming calls to a current Salesforce API version.
* Upgrade the embedded CometD client and matching Jetty HTTP client jars
together, and adjust the connector code if the APIs changed.
* Check whether PushTopic-based streaming is still the right approach, or if a
newer Salesforce event model fits better.
* Improve automated tests so the connector can be checked without only relying
on manual credentials.
h3. How to test
Build the Salesforce connector module. Connect it to a Salesforce sandbox with
a modern connected app setup. Check that login works, that lead create or
update still works, and that streaming events are received when configured.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
