This release corrects the behavior of the sanity-check URL for two scenarios:
The endpoint must be enabled in the API proxy with the SanityCheckEnabled variable with the value of true.
The endpoint now correctly handles the SAP client value.
Read more about the SAP client feature at the feature documentation.
The enosix team has completed testing to ensure compatibility of the latest enosix apps with the Salesforce Summer ‘26 release. Below are the key details of the testing process and outcomes:
Regression Testing:
Products Tested:
Mobile App Compatibility:
The enosix team remains committed to ensuring our solutions deliver seamless integration and superior performance. For any questions or support, please contact our team.
Support portal: https://go.enosix.com/support
[Feature]: Swagger API Testing Security and Usability Improvements
This release introduces API testing using a secured API key in Swagger API documentation.
Swagger now supports API key authentication. Users can authenticate in Swagger using the API key flow. This aligns interactive documentation with how protected APIs are actually secured.
Swagger “Try It Out” can be controlled by configuration. Teams can enable or disable Swagger’s live testing capability per environment. This helps keep production documentation visible while preventing unauthorized test execution.
Detailed documentation can be found here: Swagger UI
When a request is made to the /auth-payload endpoint for api proxies or via ?link-function=auth-payload for Proxies, Link validates the provided credentials against the SAP backend before issuing a delegated auth token. If the credentials are invalid or missing, a 401 Unauthorized response is returned.
[Feature]: This release introduces strict query parameter validation in the API Proxy to prevent query parameter injection into downstream SAP requests. The change addresses an issue where encoded characters (e.g., %26 for &) could be used to pass additional parameters.
Allows only below-listed query parameters, and any additional parameters passed on request are dropped
cid query string parameter will override the x-enosix-cid extension of the Open API Specification for the endpoint.x-enosix-cid extension in the Open API Specification.Ability to pass CID as Query Param.
Added support for passing cid as a query parameter to the SAP backend. The following validation rules have been added for the cid parameter:
SwaggerEnabled property that allows you to control whether the Swagger UI and OpenAPI Specification endpoints are exposed for each API Proxy. Setting SwaggerEnabled: true enables these documentation endpoints, which is useful for development and testing environments. By default, Swagger endpoints are disabled. See the Swagger UI for full details.The enosix team has completed testing to ensure compatibility of the latest enosix apps with the Salesforce Spring ‘26 release. Below are the key details of the testing process and outcomes:
Regression Testing:
Products Tested:
Mobile App Compatibility:
The enosix team remains committed to ensuring our solutions deliver seamless integration and superior performance. For any questions or support, please contact our team.
Salesforce has announced several certificate-related changes in 2026 that may generate questions from customers. enosix has reviewed these changes and assessed the impact across our product line. No customer-facing disruptions have been observed to date, and our architecture minimizes exposure to these changes. Below is a summary of each change and how it relates to enosix products.
Salesforce has transitioned to issuing certificates chained from the DigiCert Global Root G2. Any certificate issued by Salesforce after February 5, 2026 will be chained to this new root in most environments. Salesforce recommends that organizations adopt the Mozilla Root Certificate Set to future-proof their trust stores.
Salesforce Apps (Surface, Transact, Commerce, SDK, Sync): enosix integrations with SAP are built on Named Credentials and Callouts, not direct API client connections. Salesforce manages the outbound TLS trust chain for Named Credential callouts, so no customer action is required for these products. Self-signed certificates and CA-signed certificates that you upload to your org are not in scope for this change.
enosix Link: The enosix Link appliance has been patched to include the latest root certificate updates, including DigiCert Global Root G2. Customers should review the Link release announcements and ensure they are running the latest version. Customers not using the stable (automatic update) channel should update to the latest release to ensure continued compatibility.
enosix Connect: The enosix Connect appliance has been patched to support the latest root certificate updates. Customers should review the Connect release announcements and ensure they are running the latest version. Customers not using the stable (automatic update) channel should update to the latest release to ensure continued compatibility.
Effective June 15, 2026, Chrome will mandate a strict separation between server and client authentication certificates ("dual-use" ban). This impacts customers using mutual TLS (mTLS) with Salesforce, requiring that client certificates are not sourced from the same public roots used for website trust.
enosix products do not use mTLS for connectivity between Salesforce and SAP. This change has no impact on enosix integrations. Customers who have implemented custom mTLS configurations outside of enosix products should review the Salesforce-supported CAs for Client Auth EKUs and audit their mTLS usage independently.
To align with industry standards, Salesforce is reducing maximum TLS server certificate lifespans in phases:
| Date | Maximum Lifespan |
|---|---|
| March 15, 2026 | 200 days |
| March 15, 2027 | 100 days |
| March 15, 2029 | 47 days |
This means certificates will be renewed more frequently. Some CA vendors have already begun issuing 200-day certificates.
Salesforce Apps (Surface, Transact, Commerce, SDK, Sync): Certificate renewal is managed entirely by Salesforce for Named Credential connections. No customer action is required.
enosix Link & Connect: Appliance updates include support for more frequent certificate rotations. Customers should stay current on the latest releases to ensure their appliances handle renewed certificates seamlessly. Customers not using the stable (automatic update) channel should regularly check for and apply the latest updates.
| Change | Effective Date | enosix Impact | Customer Action |
|---|---|---|---|
| Root Certificate → DigiCert Global Root G2 | Feb 5, 2026 | No disruption observed | Link & Connect: update to latest release if not on stable channel |
| Dual-use Certificate Ban (mTLS) | June 15, 2026 | No impact (enosix does not use mTLS) | None for enosix products |
| Certificate Lifespan → 200 days | March 15, 2026 | No impact for Named Credential integrations | Link & Connect: stay current on releases |
For any questions or support, please contact the enosix team.