Research library

Standards checked: November 3, 2026

B2B Storefront Identity Federation and Buyer Provisioning

For Educational and Informational Purposes Only — Not Legal or Financial Advice.

Commerce Systems Review is a free, vendor-neutral educational library. This guide is general technical research, not legal, tax, accounting, financial, security, compliance-certification, or individualized implementation advice. The standards cited define protocol behavior; they do not approve a particular identity architecture or access policy.

Standards checked: November 3, 2026.

B2B storefront access crosses two different questions: who authenticated this person? and what may this person do for a particular company or location? A successful single sign-on (SSO) exchange answers the first question. It does not by itself establish that the person belongs to the right buyer account, may see its catalog, can submit an order, or still needs access.

Treat the identity provider, commerce account model, and any directory-provisioning path as separate systems with explicit contracts. The goal is a traceable relationship among an external identity, a commerce buyer record, an approved company or location membership, and the commerce permissions that apply there.

Separate authentication, provisioning, and commerce authorization

OpenID Connect (OIDC) defines an identity layer for authentication on top of OAuth 2.0. SAML defines profiles for exchanging authentication and related messages, including browser single sign-on. SCIM defines a schema and HTTP protocol for provisioning identity resources across systems. These standards address different exchanges; adopting a sign-in protocol does not automatically create a buyer directory or keep its memberships current.

Write down the systems of authority before selecting an integration pattern:

ConcernRecord or decision to identify
AuthenticationIdentity provider, protocol, issuer or entity identity, registered client or service-provider configuration, and supported sign-in path.
External person keyThe issuer-scoped subject or other protocol-defined identifier used to recognize the same person on later sign-ins.
Commerce personThe buyer/customer record that represents the person in the storefront.
Business relationshipThe approved company, purchasing location, and membership or role through which that buyer participates.
AuthorizationThe commerce-side rules that determine catalog visibility, pricing context, order permissions, and any approval rights.
ProvisioningThe process that creates, updates, suspends, or removes user and group records, and the acknowledgement or exception evidence it returns.

The commerce platform may own company/location membership and buyer roles even when a customer’s identity provider authenticates the person. Conversely, a provisioned user or directory group is input to a mapping; it is not proof that every mapped storefront permission is appropriate. Choose a clear owner for each relationship and record the process that approves a new association.

Choose a supported sign-in contract

The OpenID Connect Core 1.0 specification describes authentication and identity claims, while the OASIS SAML 2.0 Profiles standard defines profiles for SAML message exchanges, including Web Browser SSO. First confirm which protocol versions and profile details both the identity provider and commerce application actually support. A protocol label alone does not establish compatible claims, subject identifiers, account linking, session behavior, logout, or administrative provisioning.

For an OIDC integration, document the expected issuer, client identifier and audience, exact redirect URI, required claims, and how the application validates the response. RFC 9700, the IETF’s January 2025 Best Current Practice for OAuth 2.0 Security, discusses current security threats and protections such as exact redirect handling, authorization-code protections, and defenses when a client communicates with multiple authorization servers. Use the standard as a review starting point with the responsible identity and application teams; this article is not a security configuration checklist or certification.

For a SAML integration, record the entity identifiers, assertion consumer endpoint, subject format, required attributes, signing-key or certificate rollover process, and which party owns metadata changes. Confirm that the configured profile and trust settings match both sides’ current documentation. Make a controlled change plan for certificate rollover or endpoint changes so that sign-in failures can be distinguished from provisioning delays or a changed buyer relationship.

Support the protocols and options that a selected implementation documents. Avoid promising universal single logout, group delivery, automatic company matching, or just-in-time account creation from the mere presence of SAML or OIDC.

Bind a buyer to a durable external identity

An account link should use the issuer and subject together, not a display name or email address alone. In OIDC, the sub claim is specified as a locally unique, never-reassigned identifier within its issuer. Store the validated issuer and subject as the external identity key, then map that pair to the commerce buyer record. A subject from another issuer is a different identity until an authorized process explicitly links it.

Email can be useful for contact and invitation workflows, but addresses can change, be reassigned, or appear in more than one organization’s directory. Do not silently attach a returning federated identity to an existing commerce buyer solely because the email strings match. Define how an authorized buyer or administrator proves a link, how duplicate records are reviewed, and what evidence is kept if an identity provider changes or merges its subjects.

Keep the identity link separate from company access. A single authenticated person may have approved memberships in more than one company or location. Record the actual commerce relationship and its authority: for example, a maintained organization-to-commerce ID crosswalk, the source of the membership decision, its scope, and the effective state. Do not infer a company relationship from an email domain or infer purchasing rights from a successful login.

Treat SCIM as a provisioning contract

The SCIM Core Schema, RFC 7643, defines user and group resource fields. Its externalId is supplied by the provisioning client, is scoped to that provisioning domain, and can help the client relate a resource across systems. It is not automatically the same key as an OIDC sub; explicitly map the directory identity to the federated login identity and commerce buyer record.

The SCIM Protocol, RFC 7644, defines operations for creating, querying, replacing, partially updating, and deleting resources, including users and groups. Decide which resources and attributes your selected service actually supports. Document the source of each mapped field, allowed transformations, destination behavior, accepted response, and reconciliation procedure. SCIM protocol support does not establish that a commerce platform accepts every standard field, group structure, or operation.

Do not assume that a user’s active flag has one universal operational meaning. RFC 7643 says the service provider determines the definitive meaning; a typical example is that true permits login and false means the account is suspended. Confirm how the destination implements suspension and deletion, how those states interact with an existing browser session, and whether separate session or token controls are needed. Keep deletion, suspended access, and removal from one company distinct in the organization’s own model.

Just-in-time creation at first login can shorten initial setup, but it is not a replacement for an ongoing lifecycle contract. It may create a person record without the intended company, location, or purchasing role. If the chosen systems use both first-login creation and SCIM, define which path creates each record and how the second path finds it without creating a duplicate. If they use SCIM only, define what a buyer sees when provisioning has not completed. In either case, fail safely when the identity is known but the commerce relationship is absent or ambiguous.

Map groups and attributes to bounded company access

Create an explicit mapping table rather than translating every incoming group into a commerce permission by name. For each approved source group or attribute, record its owner, meaning, target company or location, resulting commerce role, precedence, and removal behavior. Include a deny or exception path for unknown groups, conflicting memberships, missing attributes, and a person linked to several buyer contexts.

SCIM group membership can communicate directory relationships, but a group name is not a commerce policy. Use a maintained mapping reviewed by the teams that own buyer access. Prefer allowlisted mappings with a narrow target scope; reject or queue unknown values for review rather than granting a broad fallback role. Store the mapping version or change reference with the resulting membership so an operator can explain why a buyer received a particular access state.

Keep these outcomes separate in logs and support tooling:

  1. The identity provider authenticated a subject.
  2. The subject matched or was linked to one commerce buyer record.
  3. The buyer had a current approved company and location relationship.
  4. The commerce platform evaluated that relationship for the requested action.
  5. The requested storefront action completed, was rejected, or remains pending.

This sequence helps staff distinguish an authentication failure from an unknown buyer, a stale membership, a role-mapping conflict, or an order that was not accepted. A generic “SSO failed” message can obscure which operator owns the repair.

Design offboarding and recovery around observed state

Write an offboarding matrix for the events that matter to your organization: a person leaves a customer company, changes location, loses one purchasing role, is suspended by the identity provider, or has a duplicate or compromised identity reported. For each event, specify who initiates and approves the change, which directory or commerce record changes, how the result is observed, whether existing sessions are affected, and who closes an incomplete handoff.

SCIM PATCH, replacement, and deletion operations have defined protocol behavior, but delivery of a request is not evidence that a downstream buyer lost the intended access. Compare the response and subsequent resource state. Make retries recognizable, retain the directory and commerce identifiers, detect repeated or out-of-order updates, and reconcile unresolved differences against the designated authority. Route ambiguous company membership or a missing destination record to a named review queue rather than choosing an account from partial data.

Keep separate recovery paths for an identity-provider outage, an expired or invalid signing key, a SCIM authorization or endpoint failure, a rejected attribute update, an incorrect group-to-role mapping, and an active storefront session after deprovisioning. Record the last observed success, affected issuer or provisioning domain, destination state, responsible owner, and a tested restoration step. Use your own access policy and approved emergency-access procedures; do not create an untracked bypass to keep orders moving.

Test the identity-to-order boundary

Use non-production tenants and synthetic people, companies, locations, and items. Test the complete journey from login through an attempted storefront action, not only the protocol callback or SCIM response.

ScenarioEvidence to compare
First sign-in before and after provisioningValid issuer/subject link, one buyer record, expected company context, and a clear pending or exception state when membership is missing.
Same email from two identity providersSeparate issuer-scoped identities unless an authorized, reviewed link exists; no automatic buyer merge.
One buyer in two companies or locationsCorrectly scoped memberships and role selection; no cross-company catalog or order access.
Group added, renamed, or removedReviewed mapping version, resulting commerce role, rejected unknown group, and observed removal behavior.
Directory suspension, SCIM deletion, or one-company removalDifferent expected outcomes, acknowledged destination state, and an explicit decision about existing sessions.
Delayed, repeated, or conflicting updateDuplicate recognition, source timestamp/version evidence, reconciliation owner, and no accidental reactivation.
Redirect, issuer, metadata, or signing-key changeApproved configuration, validation result, planned rollover, and a usable recovery route.
IdP or provisioning endpoint unavailableAccurate sign-in/provisioning distinction, support handoff, and no unapproved fallback access.

For each test, retain expected and observed identity keys, company/location relationships, permission results, protocol or provisioning response, and the exception owner. Use the results to adjust your own implementation and operating policies; passing these examples is not a universal security or compliance conclusion.

Related guides

Customer-specific catalogs and contract pricing covers the company and location context applied after identity resolution. PunchOut cart returns follows a buyer’s procurement session and cart handoff. Feature rollouts discusses evaluation context for a changed storefront experience; a rollout flag does not replace authorization. Bulk-order accessibility covers the buyer-facing interaction after the correct purchasing context is available. Data synchronization observability covers shared freshness and repair practices across systems.

First-party standards register and limits

These standards were opened and reviewed on November 3, 2026. Publication dates below identify the referenced edition, not a claim that a new revision was issued on the review date.

The mapping ledger, role review, lifecycle tests, and exception queue in this guide are proposed operating practices. Confirm which profiles, resource fields, group behavior, session controls, and provisioning operations are supported by the products and policies in your environment. This guide does not certify an implementation or provide legal, tax, accounting, financial, security, or individualized advice.

Continue reading