Challenge: When Customer Access Meets Strict Data Boundaries
P&G's multi-store commerce environment presented a set of identity, data-governance, and integration requirements that its existing setup could not address independently.
- No Native Auth0 Integration: BigCommerce did not natively support Auth0 as an identity provider, requiring a dedicated integration to establish the authentication flow.
- Storefront Had to Be Fully Gated: First and last names were maintained in P&G's internal consumer data platform, not Auth0. This separation had to remain intact throughout the account creation process.
- Standard SSO Could Not Complete Provisioning: Because Auth0 tokens omitted the names required by BigCommerce, a conventional SSO connection alone could not provide all the information needed to create customer records.
- Storefronts Required Independent Identity Environments: More than 15 live stores, alongside their staging environments, required separate Auth0 instances to preserve brand-level separation.
- Security Reviews Governed Data Exchange: The implementation had to meet third-party security and privacy assessment requirements, including minimum-disclosure rules for information exchanged between systems.
- Traffic Demanded a Resilient Design: The architecture had to accommodate 55,000 to 70,000+ monthly login and registration events, with resilience during traffic peaks.
The Solution: Connecting Identity and Commerce Without Compromising Privacy
miniOrange Cloud CIAM provided the integration layer for P&G's BigCommerce storefronts, with a tailored implementation to address the requirements of its identity architecture.
JWT-Based Single Sign-On and Single Logout
JWT-based Single Sign-On (SSO) and Single Logout (SLO) connected Auth0 with each BigCommerce storefront, establishing the authentication handoff between the identity provider and the commerce platform.
Middleware Supplied the Required Profile Attributes
During sign-in, the middleware retrieved first and last names from the internal consumer data platform and supplied them to the BigCommerce account creation flow. The attributes did not need to be included in Auth0 tokens.
Separate Auth0 Instances Preserved Brand Isolation
Each storefront retained its own Auth0 instance across production and staging. This maintained independent identity environments while following a consistent integration approach.
Attribute Retrieval Followed Data-Governance Requirements
The integration used the internal consumer data platform as the source of customer profile details. This allowed the provisioning flow to access the information it required without adding those attributes to Auth0 tokens.
The Results: Making Customer Provisioning Work at Scale
The implementation addressed the account creation gap and established a repeatable integration pattern for the storefront network.
- Account Creation With Required Attributes: BigCommerce received the names needed to create customer records through the middleware flow.
- Consistent Authentication Integration: JWT-based SSO and SLO connected Auth0 with the commerce storefronts.
- Independent Brand Environments: Separate Auth0 instances maintained the required separation between storefronts and their staging environments.
- A Defined Profile Retrieval Path: Customer attributes were sourced from the internal consumer data platform rather than added to Auth0 tokens.
- A Design Informed by Traffic Requirements: The deployment was planned around the stated monthly authentication volume and the need to withstand traffic peaks.
About P&G
Procter & Gamble (P&G) is a global consumer goods company with a portfolio of trusted brands spanning multiple product categories. Its products reach consumers across markets worldwide.
Its digital commerce operations connect consumers with brands through online storefronts. These experiences rely on identity and account processes that accommodate commerce requirements alongside internal data-governance policies.
