Skip to main content

6 posts tagged with "commerce"

View All Tags

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.


1. Root Certificate Transition to DigiCert Global Root G2 (Effective February 5, 2026)

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.

Impact on enosix Products

  • 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.


2. Deprecation of Dual-use Certificates (Effective June 15, 2026)

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.

Impact on enosix Products

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.


3. Certificate Lifespan Reductions (Starting March 15, 2026)

To align with industry standards, Salesforce is reducing maximum TLS server certificate lifespans in phases:

DateMaximum Lifespan
March 15, 2026200 days
March 15, 2027100 days
March 15, 202947 days

This means certificates will be renewed more frequently. Some CA vendors have already begun issuing 200-day certificates.

Impact on enosix Products

  • 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.


Summary

ChangeEffective Dateenosix ImpactCustomer Action
Root Certificate → DigiCert Global Root G2Feb 5, 2026No disruption observedLink & Connect: update to latest release if not on stable channel
Dual-use Certificate Ban (mTLS)June 15, 2026No impact (enosix does not use mTLS)None for enosix products
Certificate Lifespan → 200 daysMarch 15, 2026No impact for Named Credential integrationsLink & Connect: stay current on releases

Additional Resources

For any questions or support, please contact the enosix team.

Store Configuration Component Initializes Default Values

The Initialize button appears when a new configuration option is introduced; clicking on this button will set the default values for any unset settings.

B2B Commerce _1

Provides the enosix Product Detail Template component to demonstrate integration with enosix Product Detail API

Use the enosix Product Detail Template as reference to return real-time data from SAP for your Product Detail page.

Confirmed checkout with Salesforce B2B Synchronous Checkout

enosix B2B integration has been tested inside the new Salesforce B2B Synchronous Checkout flow to provide the same checkout process; however, it is faster without the delayed message.

Updated the enosix B2B Commerce Package

The “enosix B2B Commerce” is a single package installed. The Standard and Professional packages will not be required or installed.

B2B Commerce_2

👉 The following features were improved:

1️⃣ Cart Bubble

The cart bubble includes the total count of items currently in your cart and is updated regardless of where you add products to your cart.

2️⃣ Complete Order

You can now see the “Total” amount for a completed order after the order has been completed and processed in the application on the Item Details Page.

3️⃣ Date Available

The Product Availability data is provided by the enosix Product Detail API.

  • [Feature]: Store Configuration Component Initializes Default values
  • [Feature]: Provides the enosix Product Detail Template component to demonstrate integrating with enosix Product Detail API
  • [Update]: Confirmed checkout with Salesforce B2B synchronous checkout
  • [Update]: Updated the enosix B2B Commerce package
  • [Bugfix]: Cart Bubble is updated when products are added to cart
  • [Bugfix]: Total is populated when viewing completed order
  • [Bugfix]: Data Available is being displayed for product details

Announced on Dec 10th, 2021 the Zero Day Log4j vulnerability CVE-2021-44228, is affecting systems worldwide. enosix has reviewed its systems and has yet to detect any platforms, apps, or services that are affected by this vulnerability.

Salesforce is conducting its own analysis of its systems. Any Salesforce apps provided by enosix (Surface, Transact, Commerce, CPQ) are not using log4j and are not affected. Salesforce will provide updates to the Salesforce platform, if needed.

The enosix connect platform does not utilize java or the log4j libraries and is not affected. Your IT department should review any other apps you are running in the SAP BTP platform, see SAP Note 3130476

enosix Link does not utilize java or the log4j libraries and is not affected. SAP Note 3130868 details that none of the SAP Cloud Connector versions contain the affected log4j-core and are not affected.

enosix will continue to review our systems and provide assistance. We advise that all computer systems operators review their systems that may be affected and take the recommend steps to patch any affected software.

Address bugs and repair deployments since the Salesforce Commerce changes

  • [Update]: Add support for Winter '22
  • [Bugfix]: Fix price/unit on checkout screen
  • [Bugfix]: Fix the cart total icon when item counts are updated

Incremental update to expand Tax integration and pricing.

  • [Feature]: Original price displayed on custom product detail component
  • [Feature]: Allow for configuring multiple jurisdiction cart tax integration from SAP.
  • [Update]: Added busy indicator when calculating price and availability from SAP on product detail page.
  • [Update]: 1.3.2 - Support for Spring '21
  • [Bugfix]: PO Number from checkout saved to order even if blank
  • [Bugfix]: Cart pricing error on first checkout after login
  • [Bugfix]: Doc flow on order summary component is now populated correctly
  • [Bugfix]: Missing total value on item detail on order summary

Add functionality for syncing product and account data. Completes the entry tier. Bug fixes, additional functionality important for demos - in particular syncing bill to/ship to and pricing/ATP on product detail page.

  • [Feature]: Bill to and ship to sync from SAP and are properly captured on order when selected
  • [Feature]: Real-time pricing, ATP, and tiered pricing on product detail page.
  • [Feature]: Confirm item availability on cart before creating order.
  • [Feature]: Improved branding of store configuration control.
  • [Update]: Resolved security review issues for app store
  • [Update]: Moved line item component to use new line item RIO.