roeiad's avatar
roeiad
Cloud Apps
12-08-2025
Status:
New Idea

Native Support for Salesforce Connected App Authentication

Salesforce has announced that API Access Control must be enforced, and once fully enforced, the username/password + security token method will no longer be permitted for API integrations.

https://help.salesforce.com/s/articleView?id=005228838&type=1

While the current Sisense guidance allows us to continue using token-based authentication, we belive this is only a temporary gap in Salesforce’s enforcement. We expect that Salesforce will require all integrations to authenticate exclusively through an allowlisted Connected App using OAuth.

This is not a feature request in the traditional sense. It is a compliance requirement dictated by Salesforce’s security model, and other analytics and reporting tools that integrate with Salesforce already support Connected App–based OAuth authentication natively.

To ensure long term compatibility and security, Sisense needs to provide:

  1. Native support for OAuth via Salesforce Connected App, without requiring manual JDBC string assembly or custom development
  2. A UI-driven configuration aligned with Salesforce’s allowlisting and API Access Control policies
  3. Clear guidance for customers migrating away from token-based authentication

Without this capability, Sisense will no longer be able to integrate with Salesforce once Salesforce completes enforcement.

Please escalate this as a priority compliance feature.

Authentication
Data Connectors

1 Comment

  • Oleksandr_K's avatar
    Oleksandr_K
    Sisense Employee
    01-12-2026

    Hi , 

    Thank you for raising this and for sharing Salesforce’s announcement -changes had been reviewed carefully.

    At this time, Sisense does not have plans in the upcoming quarter to invest in additional Salesforce authentication mechanisms beyond what is currently supported.

    Regarding Salesforce’s announcement about changes to the “Use any API Client” permission behavior, our team has validated that Sisense connectivity to Salesforce remains stable, and there are no blocking or breaking changes required for Sisense to continue operating under the updated Salesforce enforcement model.

    While Salesforce is evolving its security posture, the current Sisense-supported authentication methods remain functional and compliant based on Salesforce’s documented behavior at this stage.

    For customers who may be impacted or want to proactively prepare, we have already published guidance outlining the change and its implications:
    https://docs.sisense.com/main/SisenseLinux/salesforce-change-and-impact.htm

    We will continue to monitor Salesforce’s enforcement timeline and requirements closely, and we’ll reassess if and when concrete, mandatory changes are introduced that directly impact Sisense integrations.

    Thanks!