---
schema_version: "1"
id: 5bb388f2e14e20011d6a5666647ce85fc7b77e6952380b2e5319e4a6cecc9a65
title: Hybrid Authentication Overview
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/commerce-cloud/commerce-api/guides/hybrid-authentication.md
canonical_url: https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/hybrid-authentication.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 916533744bc24bab76d409a5a7426a4189df32cb129dd9aca49091f902e36633
products:
  - Composable Storefront
  - Salesforce APIs
---
# Hybrid Authentication Overview

Starting with B2C Commerce version 25.3, hybrid authentication (Hybrid Auth) replaces Plugin SLAS.

Hybrid Auth keeps SFRA/SiteGenesis session state (`dwsid`) and SLAS authorization state (JWT) synchronized for storefronts that span multiple runtimes. It applies to all hybrid storefront architectures: Storefront Next, PWA Kit (Composable Storefront), and SFRA/SiteGenesis.

The [Shared Hybrid Auth Setup](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/hybrid-auth-shared-setup.md) covers the architecture-neutral steps that every hybrid storefront needs. After you complete it, follow the implementation guide for your storefront architecture.

## What Hybrid Auth Solves

- Synchronizes shopper auth context between platform-rendered pages and headless pages
- Replaces Plugin SLAS with a platform-native implementation
- Enables consistent handling for Shopper Context, session extension, and Do-Not-Track (DNT) synchronization
- Supports eCDN-based traffic splitting for phased headless rollouts

**note:** For non-PWA Kit headless storefronts, if you're using Hybrid Auth and the `dwsid` cookie exists, include the `sfdc_dwsid` header with the `dwsid` cookie value on all SCAPI calls.

## Benefits

- **Platform-native, no Plugin SLAS**: Launch faster with out-of-the-box authentication that automatically synchronizes data between SFRA/SiteGenesis and headless pages—no Plugin SLAS required.
- **Seamless shopper experience**: Shoppers move across your hybrid site with no disruption or data loss, including synchronized Shopper Context attributes and consistent analytics.
- **Full support for all templates**: A fully productized solution for both SFRA and SiteGenesis eases your path to Composable Storefront.

## Architecture

![B2C Commerce hybrid authentication architecture with SFRA/SiteGenesis and headless storefront components](https://developer.salesforce.com/docs/media/commerce-api/hybrid-auth-architecture.png '{"class": "image-lg"}')

## Next Steps

1. Choose your architecture in [Select Your Storefront](https://developer.salesforce.com/docs/commerce/b2c-commerce/guides/hybrid-auth-select-storefront.md). For an existing PWA Kit v2.x project, see [Hybrid Auth Implementation with PWA Kit v2.x](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/hybrid-auth-pwa-kit-v2.md).
2. Complete the [Shared Hybrid Auth Setup](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/hybrid-auth-shared-setup.md)—the architecture-neutral steps that every hybrid storefront needs.
3. Follow the setup path for your architecture: [Storefront Next Automated Setup](https://developer.salesforce.com/docs/commerce/b2c-commerce/guides/hybrid-auth-quick-start.md) (Storefront Next only) or [Manual Setup](https://developer.salesforce.com/docs/commerce/b2c-commerce/guides/hybrid-auth-manual-setup.md) (all other architectures).
4. Review per-environment differences and route ownership in [Hybrid Auth Environments and Routing](https://developer.salesforce.com/docs/commerce/b2c-commerce/guides/hybrid-auth-environment-matrix.md).
5. Resolve issues with [Hybrid Auth Troubleshooting](https://developer.salesforce.com/docs/commerce/b2c-commerce/guides/hybrid-auth-troubleshooting.md).