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://h...
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!