The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Salesforce disables two Connected Apps over suspicious access token use (opens in a new tab)

You will learn that Salesforce disabled the Talent Rover and GoFundMe Pro Connected Apps and managed packages over suspicious access token use, and what the company said about their status.

Why read this

Read it if your orgs use either integration.

Salesforce disabled integrations with two Connected Apps in the week of November 10, 2025, after identifying suspicious use of access tokens linked to the third-party providers. The first advisory, posted on November 10, covered Talent Rover, a product owned by Bullhorn. Salesforce disabled its Connected Apps and managed packages as a precaution and said the issue did not stem from a vulnerability in the Salesforce platform.

The same day, Salesforce re-enabled the Talent Rover Connected Apps and managed packages after Bullhorn completed security remediation. The second advisory, issued November 11, applied the same measures to the GoFundMe Pro Connected App and its associated managed packages. Salesforce again said the core platform was not at fault.

Salesforce and GoFundMe are investigating the activity together. The GoFundMe Pro integrations will stay unavailable until remediation is complete and GoFundMe has shown they can be restored safely. Salesforce said it will notify affected customers without undue delay if it finds unauthorized access to their data. At the time of writing, GoFundMe Pro remained disabled, and the article notes the earlier Connected App problems of 2025, which led Salesforce to harden Connected App security.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?

Architecting customer portals beyond Experience Cloud licensing and API limits (opens in a new tab)

Readers will learn how to evaluate four portal architectures against Experience Cloud by weighing licensing costs, API budgets, and data synchronization trade-offs.

Why read this

The piece provides a structured set of questions to assess security, visibility, and failure modes for each approach.

The article examines four architectural approaches for building customer portals that do not rely on Experience Cloud licenses. It contrasts running the portal directly on the Salesforce platform using licensed external users or headless identity APIs, connecting to a live Salesforce database through a third party, syncing records to an external database, or migrating customer data entirely to a different system like Microsoft Dataverse.

Each model carries distinct operational trade-offs. On-platform deployments enforce native security and real-time data but require per-user licensing and consume administrative capacity. Off-platform live connections avoid licensing fees but draw heavily from the rolling 24-hour API limit and introduce OAuth token security risks. Synced copies reduce API consumption and provide outage resilience but risk data staleness and write collisions, requiring careful reconciliation policies.

To navigate these options, the author recommends evaluating every vendor against five criteria: where customer data resides, how Salesforce classifies portal visitors, which layer enforces record visibility, the typical API cost per page or acceptable sync lag, and procedures for handling connection failures or token revocation. The analysis concludes that Experience Cloud remains the only true single system of record, while alternatives simply shift architectural responsibilities to API management, data governance, or external security configurations.

Read the original at dev.to (opens in a new tab)

Worth reading?