Install AI Tools

B2C Commerce tools, documentation, and skills for your assistant.

Claude

Using Claude Desktop? See Claude Desktop (Cowork) setup.

Install the plugin Recommended

bash
claude plugin marketplace add SalesforceCommerceCloud/b2c-developer-tooling
claude plugin install b2c-dx-mcp@b2c-developer-tooling

Start a new Claude Code session. To install for the current project only, run it from your project directory with --scope project.

Turn on auto-update

Claude Code does not auto-update third-party marketplaces by default, so installed plugins stay on the version you installed. To get new releases automatically, run /plugin, open Marketplaces, select b2c-developer-tooling, and choose Enable auto-update. Claude Code then checks for updates when a session starts; run /reload-plugins or start a new session to load them.

Manual MCP setup
bash
claude mcp add --transport stdio --scope user b2c-dx-mcp -- npx -y @salesforce/b2c-dx-mcp@latest

Start a new session. To configure the current project only, run it from your project directory with --scope project. See Claude Code MCP setup.

Codex/ChatGPT

Using the ChatGPT desktop app (ChatGPT Work)? See ChatGPT Work setup.

Install the plugin Recommended

bash
codex plugin marketplace add SalesforceCommerceCloud/b2c-developer-tooling
codex plugin add b2c-dx-mcp@b2c-developer-tooling

Start a new Codex session in your project. Codex plugins also work in ChatGPT Work.

Manual MCP setup
bash
codex mcp add b2c-dx-mcp -- npx -y @salesforce/b2c-dx-mcp@latest

Or add this to ~/.codex/config.toml (or $CODEX_HOME/config.toml if customized):

toml
[mcp_servers.b2c-dx-mcp]
command = "npx"
args = ["-y", "@salesforce/b2c-dx-mcp@latest"]

Start a new session. See Codex MCP configuration.

VS Code

Install the plugin Recommended

  1. Open the Command Palette (Cmd/Ctrl+Shift+P) and run Chat: Install Plugin from Source.
  2. Enter SalesforceCommerceCloud/b2c-developer-tooling.
  3. Select b2c-dx-mcp and follow the installation prompts.
  4. Start a new chat in GitHub Copilot.
Manual MCP setup

Add this to .vscode/mcp.json in your workspace:

json
{
  "servers": {
    "b2c-dx-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@salesforce/b2c-dx-mcp@latest"]
    }
  }
}

See VS Code MCP setup.

Copilot CLI setup

Cursor

Reload the MCP server in Cursor after installation.

Manual MCP setup

Add this to .cursor/mcp.json in your project:

json
{
  "mcpServers": {
    "b2c-dx-mcp": {
      "command": "npx",
      "args": ["-y", "@salesforce/b2c-dx-mcp@latest"]
    }
  }
}

For all projects, use ~/.cursor/mcp.json instead.

See Cursor's MCP documentation.

OpenCode

Add this to opencode.json in your project:

json
{
  "mcp": {
    "b2c-dx-mcp": {
      "type": "local",
      "command": ["npx", "-y", "@salesforce/b2c-dx-mcp@latest"],
      "enabled": true
    }
  }
}

Restart OpenCode. For all projects, use ~/.config/opencode/opencode.json. See OpenCode MCP setup.

Gemini

Run:

bash
gemini mcp add --scope user b2c-dx-mcp -- npx -y @salesforce/b2c-dx-mcp@latest

Start a new Gemini CLI session. To configure the current project only, run it from your project directory with --scope project. See Gemini CLI MCP setup.

No separate skills plugins needed.

Other clients and manual setup →
Skip to content
View as Markdown
View as Markdown

SLAS Commands ​

Commands for managing Shopper Login and API Access Service (SLAS) tenants, clients, password action templates, identity providers, and shopper sessions. For client types, user roles, and shopper authentication flows, see Salesforce's Authorization for Shopper APIs.

TIP

New to SLAS? The SLAS guide walks through common tasks step by step.

Global SLAS Flags ​

These flags are available on all SLAS commands:

FlagEnvironment VariableDescription
--tenant-idSFCC_TENANT_ID(Required) SLAS tenant ID (organization ID)

Authentication ​

SLAS commands work without any API client configuration: you sign in with your Account Manager account in the browser.

For automation or CI/CD, provide your own API client credentials.

Required Roles ​

Auth MethodRoleConfigured On
Built-in client (default)SLAS Organization AdministratorYour user account
User AuthenticationSLAS Organization AdministratorYour user account
Client CredentialsSandbox API UserThe API client

The role must have a tenant filter configured for the organization you wish to manage.

Configuration ​

bash
# No configuration needed — opens browser for login
b2c slas client list --tenant-id abcd_123

# Or provide your own client ID
b2c slas client list --tenant-id abcd_123 --client-id xxx

# Client Credentials (for automation)
export SFCC_CLIENT_ID=my-client
export SFCC_CLIENT_SECRET=my-secret
b2c slas client list --tenant-id abcd_123

For complete setup instructions, see the Authentication Guide.


b2c slas token ​

Get a SLAS shopper access token for testing APIs.

Shopper authorization, login, and token requests use the shared HTTP middleware. Custom headers configured through SFCC_EXTRA_HEADERS (a JSON object) or --extra-headers apply to every step of both guest and registered flows. Use --log-level debug to include SLAS response correlation IDs when diagnosing failures.

Usage ​

bash
b2c slas token --tenant-id <TENANT_ID> --site-id <SITE_ID>

Flags ​

FlagEnvironment VariableDescriptionRequired
--tenant-idSFCC_TENANT_IDSLAS tenant ID (organization ID)Yes
--site-idSFCC_SITE_IDSite/channel IDYes*
--slas-client-idSFCC_SLAS_CLIENT_IDSLAS client ID (auto-discovered if omitted)No
--slas-client-secretSFCC_SLAS_CLIENT_SECRETSLAS client secret (omit for public clients)No
--short-codeSFCC_SHORTCODESCAPI short codeYes
--redirect-uriRedirect URINo
--shopper-loginRegistered customer loginNo
--shopper-passwordRegistered customer password (prompted interactively if omitted)No

* --site-id can be auto-discovered from the SLAS client configuration when using auto-discovery.

Flows ​

The command automatically selects the appropriate authentication flow based on whether --shopper-login and --slas-client-secret are provided:

ScenarioFlow
Guest, no --slas-client-secretPublic client guest PKCE (authorization_code_pkce)
Guest, with --slas-client-secretPrivate client client_credentials
Registered (--shopper-login), no secretRegistered login + PKCE (authorization_code_pkce)
Registered (--shopper-login), with secretRegistered login + PKCE, plus client-secret Basic auth
No --slas-client-idAuto-discovers first public client via SLAS Admin API

Registered login uses PKCE on both public and private clients

The registered-customer flow is always PKCE-protected: the /oauth2/login step presents a code_challenge, so the token exchange always sends the matching code_verifier. A private SLAS client additionally authenticates with its secret (HTTP Basic). This is why the registered flow works against both public and private clients.

Examples ​

bash
# Guest token with auto-discovery (finds first public SLAS client)
b2c slas token --tenant-id abcd_123 --site-id RefArch

# Guest token with explicit public client (PKCE flow)
b2c slas token --slas-client-id my-client \
  --tenant-id abcd_123 --short-code kv7kzm78 --site-id RefArch

# Guest token with private client (client_credentials flow)
b2c slas token --slas-client-id my-client --slas-client-secret sk_xxx \
  --tenant-id abcd_123 --short-code kv7kzm78 --site-id RefArch

# Registered customer token
b2c slas token --tenant-id abcd_123 --site-id RefArch \
  --shopper-login user@example.com --shopper-password secret

# JSON output (includes refresh token, expiry, usid, etc.)
b2c slas token --tenant-id abcd_123 --site-id RefArch --json

# Use token in a subsequent API call
TOKEN=$(b2c slas token --tenant-id abcd_123 --site-id RefArch)
curl -H "Authorization: Bearer $TOKEN" \
  "https://kv7kzm78.api.commercecloud.salesforce.com/..."

Output ​

  • Normal mode: prints the raw access token to stdout (pipeable)
  • JSON mode (--json): returns full token details:
json
{
  "response": {
    "accessToken": "...",
    "refreshToken": "...",
    "expiresIn": 1800,
    "tokenType": "Bearer",
    "usid": "...",
    "customerId": "..."
  },
  "clientId": "...",
  "siteId": "RefArch",
  "isGuest": true
}

Configuration ​

These values can also be set in dw.json:

json
{
  "tenant-id": "abcd_123",
  "short-code": "kv7kzm78",
  "slas-client-id": "my-public-client",
  "site-id": "RefArch"
}

Existing Client Selection ​

The get, update, delete, and open commands use the configured slasClientId when their positional CLIENTID is omitted. The value can come from dw.json, SFCC_SLAS_CLIENT_ID, --slas-client-id, the active instance, or a configuration plugin. A positional CLIENTID takes precedence over every configured source.


b2c slas client list ​

List SLAS clients for a tenant.

Usage ​

bash
b2c slas client list --tenant-id <TENANT_ID>

Flags ​

FlagDescriptionRequired
--tenant-idSLAS tenant ID (organization ID)Yes

Examples ​

bash
# List all SLAS clients for a tenant
b2c slas client list --tenant-id abcd_123

# Output as JSON
b2c slas client list --tenant-id abcd_123 --json

# Using environment variables
export SFCC_TENANT_ID=abcd_123
b2c slas client list

Output ​

Displays a list of SLAS clients with:

  • Client ID
  • Name
  • Type (public/private)
  • Channels

b2c slas client create ​

Create or update a SLAS client.

Usage ​

bash
b2c slas client create [CLIENTID] --tenant-id <TENANT_ID> --channels <CHANNELS> --redirect-uri <URI>

Arguments ​

ArgumentDescriptionRequired
CLIENTIDSLAS client ID (generates UUID if omitted)No

Flags ​

FlagDescriptionDefault
--tenant-idSLAS tenant ID (organization ID)Required
--channelsSite IDs/channels (comma-separated)Required
--redirect-uriRedirect URIs (comma-separated)Required
--nameDisplay name for the clientAuto-generated
--scopesOAuth scopes for the client (comma-separated)
--default-scopesUse default shopper scopesfalse
--callback-uriCallback URIs for passwordless login
--secretClient secret (generated if omitted)Auto-generated
--publicCreate a public client (default is private)false
--[no-]login-restrictedRestrict shopper login endpoints to this client (loginEpRestrict)false
--[no-]six-digit-otpUse 6-digit instead of 8-digit one-time passwords for passwordless loginfalse
--[no-]strict-client-authRequire client authentication on token requests (private clients only)false
--[no-]create-tenantAutomatically create tenant if it doesn't existtrue

Examples ​

bash
# Create a private client with specific scopes
b2c slas client create --tenant-id abcd_123 \
  --channels RefArch \
  --scopes sfcc.shopper-products,sfcc.shopper-search \
  --redirect-uri http://localhost:3000/callback

# Create a named client with custom ID
b2c slas client create my-client-id --tenant-id abcd_123 \
  --name "My Application" \
  --channels RefArch \
  --scopes sfcc.shopper-products \
  --redirect-uri http://localhost:3000/callback

# Create a public client
b2c slas client create --tenant-id abcd_123 \
  --channels RefArch \
  --default-scopes \
  --redirect-uri http://localhost:3000/callback \
  --public

# Output as JSON (useful for capturing the generated secret)
b2c slas client create --tenant-id abcd_123 \
  --channels RefArch \
  --default-scopes \
  --redirect-uri http://localhost:3000/callback \
  --json

# Restrict login endpoints and use 6-digit passwordless codes
b2c slas client create --tenant-id abcd_123 \
  --channels RefArch \
  --default-scopes \
  --redirect-uri http://localhost:3000/callback \
  --login-restricted --six-digit-otp

Notes ​

  • If --secret is not provided for a private client, one will be generated
  • The generated secret is only shown once during creation
  • Use --default-scopes for common shopper API access scopes
  • By default, the tenant is automatically created if it doesn't exist. Use --no-create-tenant to disable this behavior if you prefer to manage tenants separately
  • SLAS ignores loginEpRestrict when a client is created, so --login-restricted is applied with a second update right after creation
  • --strict-client-auth has no effect on public clients

b2c slas client get ​

Get details of a SLAS client.

Usage ​

bash
b2c slas client get [CLIENTID] --tenant-id <TENANT_ID>

Arguments ​

ArgumentDescriptionRequired
CLIENTIDSLAS client ID to retrieve. Defaults to the configured slasClientIdNo

Examples ​

bash
# Get details for the configured SLAS client
b2c slas client get --tenant-id abcd_123

# Override the configured SLAS client ID
b2c slas client get my-client-id --tenant-id abcd_123

# Output as JSON
b2c slas client get my-client-id --tenant-id abcd_123 --json

Output ​

Displays detailed information about the client including:

  • Client ID and name
  • Type (public/private)
  • Channels
  • Scopes
  • Redirect URIs
  • Callback URIs

b2c slas client update ​

Update an existing SLAS client.

Usage ​

bash
b2c slas client update [CLIENTID] --tenant-id <TENANT_ID> [FLAGS]

Arguments ​

ArgumentDescriptionRequired
CLIENTIDSLAS client ID to update. Defaults to the configured slasClientIdNo

Flags ​

FlagDescription
--tenant-id(Required) SLAS tenant ID
--nameUpdate display name
--secretRotate client secret
--channelsUpdate channels (comma-separated)
--scopesUpdate scopes (comma-separated)
--redirect-uriUpdate redirect URIs (comma-separated)
--callback-uriUpdate callback URIs (comma-separated)
--replaceReplace list values instead of appending
--privateMake the client private (generates a secret unless --secret is given)
--publicMake the client public (removes its secret)
--[no-]login-restrictedRestrict shopper login endpoints to this client (loginEpRestrict)
--[no-]six-digit-otpUse 6-digit instead of 8-digit one-time passwords for passwordless login
--[no-]strict-client-authRequire client authentication on token requests (private clients only)

Examples ​

bash
# Update the configured client name
b2c slas client update --tenant-id abcd_123 --name "New Name"

# Override the configured SLAS client ID
b2c slas client update my-client-id --tenant-id abcd_123 --name "New Name"

# Rotate client secret
b2c slas client update my-client-id --tenant-id abcd_123 --secret new-secret-value

# Add scopes (appends to existing)
b2c slas client update my-client-id --tenant-id abcd_123 --scopes sfcc.shopper-baskets

# Replace all scopes
b2c slas client update my-client-id --tenant-id abcd_123 \
  --scopes sfcc.shopper-products,sfcc.shopper-baskets \
  --replace

# Replace all channels
b2c slas client update my-client-id --tenant-id abcd_123 \
  --channels RefArch,SiteGenesis \
  --replace

# Restrict login endpoints and require strict client authentication
b2c slas client update my-client-id --tenant-id abcd_123 --login-restricted --strict-client-auth

# Convert a public client to private (prints the generated secret)
b2c slas client update my-client-id --tenant-id abcd_123 --private

Notes ​

  • By default, list values (channels, scopes, URIs) are appended to existing values
  • Use --replace to replace all values instead of appending
  • Secret rotation takes effect immediately
  • Settings you don't pass (login restriction, OTP length, strict authentication) keep their current values
  • Switching to --public removes the client secret; switching to --private generates one unless you pass --secret

b2c slas client delete ​

Delete a SLAS client.

Usage ​

bash
b2c slas client delete [CLIENTID] --tenant-id <TENANT_ID>

Arguments ​

ArgumentDescriptionRequired
CLIENTIDSLAS client ID to delete. Defaults to the configured slasClientIdNo

Examples ​

bash
# Delete the configured client
b2c slas client delete --tenant-id abcd_123

# Override the configured SLAS client ID
b2c slas client delete my-client-id --tenant-id abcd_123

# Output as JSON
b2c slas client delete my-client-id --tenant-id abcd_123 --json

Notes ​

  • Deletion is permanent and cannot be undone
  • Active sessions using this client will be invalidated

b2c slas client open ​

Open the SLAS Admin UI for a client in your browser.

Usage ​

bash
b2c slas client open [CLIENTID] --tenant-id <TENANT_ID>

Arguments ​

ArgumentDescriptionRequired
CLIENTIDSLAS client ID to open in the admin UI. Defaults to the configured slasClientIdNo

Flags ​

FlagEnvironment VariableDescriptionRequired
--tenant-idSFCC_TENANT_IDSLAS tenant ID (organization ID)Yes
--short-codeSFCC_SHORTCODESCAPI short codeYes*
--slas-client-idSFCC_SLAS_CLIENT_IDConfigured SLAS client IDNo

* --short-code can be set via SFCC_SHORTCODE environment variable or short-code in dw.json.

Examples ​

bash
# Open the SLAS Admin UI for the configured client
b2c slas client open --tenant-id abcd_123

# Override the configured SLAS client ID
b2c slas client open my-client-id --tenant-id abcd_123

# With explicit short code
b2c slas client open my-client-id --tenant-id abcd_123 --short-code kv7kzm78

Notes ​

  • Opens the SLAS Admin UI in your default browser
  • The URL is also printed to the console if the browser fails to open

b2c slas client template list ​

List the password action templates of a SLAS client for a site. Templates define the email or SMS message SLAS sends for passwordless login, password reset, and WebAuthn flows.

Usage ​

bash
b2c slas client template list [CLIENTID] --tenant-id <TENANT_ID> --site-id <SITE_ID>

Flags ​

FlagEnvironment VariableDescription
--tenant-idSFCC_TENANT_ID(Required) SLAS tenant ID
--site-idSFCC_SITE_ID(Required) Site ID. Alias: --channel-id
--slas-client-idSFCC_SLAS_CLIENT_IDClient ID when the argument is omitted
--action-typeOnly list one action type
--template-typeOnly list EMAIL or SMS templates
--columns, --extendedChoose table columns

Action types:

Action TypeUsed For
PWDLESS_LOGINPasswordless login
PWD_RESET_ACTIONPassword reset
PWD_RESET_CROSS_DEVICE_ACTIONCross-device password reset
WEBAUTHN_AUTHORIZE_USERWebAuthn user authorization

Examples ​

bash
# List all templates of a client for a site
b2c slas client template list my-client-id --tenant-id abcd_123 --site-id RefArch

# Only passwordless login templates
b2c slas client template list my-client-id --tenant-id abcd_123 --site-id RefArch --action-type PWDLESS_LOGIN

b2c slas client template get ​

Show one password action template.

Usage ​

bash
b2c slas client template get [CLIENTID] --tenant-id <TENANT_ID> --site-id <SITE_ID> \
  --action-type <TYPE> --template-type <EMAIL|SMS> --locale <LOCALE>

Examples ​

bash
b2c slas client template get my-client-id --tenant-id abcd_123 --site-id RefArch \
  --action-type PWDLESS_LOGIN --template-type EMAIL --locale en-us

b2c slas client template set ​

Create or update a password action template. A template is identified by site, action type, template type, and locale. When the template exists, only the fields you pass change.

Usage ​

bash
b2c slas client template set [CLIENTID] --tenant-id <TENANT_ID> --site-id <SITE_ID> \
  --action-type <TYPE> --template-type <EMAIL|SMS> --locale <LOCALE> [FLAGS]

Flags ​

FlagDescription
--action-type(Required) Action type (see template list)
--template-type(Required) EMAIL or SMS
--locale(Required) Template locale, for example en-us (stored in lowercase)
--nameTemplate name
--subjectMessage subject
--linkLink sent to the shopper; can include ${token}
--templateMessage body
--template-fileRead the message body from a file (- for stdin)
--fileJSON file with the template fields (channelId, actionType, templateType, locale, name, subject, link, template); flags override it

A new template needs --name, --subject, --link, and a body.

Examples ​

bash
# Create an email template for passwordless login
b2c slas client template set my-client-id --tenant-id abcd_123 --site-id RefArch \
  --action-type PWDLESS_LOGIN --template-type EMAIL --locale en-us \
  --name "Login code" --subject "Your login code" \
  --link 'https://example.com/login?token=${token}' \
  --template-file login-email.html

# Change only the subject
b2c slas client template set my-client-id --tenant-id abcd_123 --site-id RefArch \
  --action-type PWDLESS_LOGIN --template-type EMAIL --locale en-us \
  --subject "Sign in to your account"

b2c slas client template delete ​

Delete a password action template. Prompts for confirmation unless --force is given.

Usage ​

bash
b2c slas client template delete [CLIENTID] --tenant-id <TENANT_ID> --site-id <SITE_ID> \
  --action-type <TYPE> --template-type <EMAIL|SMS> --locale <LOCALE> [--force]

Examples ​

bash
b2c slas client template delete my-client-id --tenant-id abcd_123 --site-id RefArch \
  --action-type PWDLESS_LOGIN --template-type EMAIL --locale en-us --force

b2c slas tenant get ​

Show the SLAS registration of a tenant.

Usage ​

bash
b2c slas tenant get --tenant-id <TENANT_ID>

Examples ​

bash
b2c slas tenant get --tenant-id abcd_123
b2c slas tenant get --tenant-id abcd_123 --json

b2c slas tenant set ​

Register a SLAS tenant, or update its merchant and contact details. Fields you don't pass keep their current values. When the tenant is not registered yet, placeholder values are used for any field you omit.

Usage ​

bash
b2c slas tenant set --tenant-id <TENANT_ID> [FLAGS]

Flags ​

FlagDescription
--merchant-nameMerchant name
--descriptionTenant description
--contactContact name
--emailContact email address
--phoneContact phone number

Examples ​

bash
# Register a tenant
b2c slas tenant set --tenant-id abcd_123 --merchant-name "Example Store" --contact "Ops Team" --email ops@example.com

# Update the contact email
b2c slas tenant set --tenant-id abcd_123 --email support@example.com

Notes ​

  • SLAS has no API to delete or list tenants. b2c slas client create registers the tenant automatically unless you pass --no-create-tenant

b2c slas idp list ​

List the identity providers configured for a SLAS tenant.

Usage ​

bash
b2c slas idp list --tenant-id <TENANT_ID>

Flags ​

FlagDescription
--show-secretInclude IDP client secrets in the output (masked by default)
--columns, --extendedChoose table columns

b2c slas idp get ​

Show one identity provider.

Usage ​

bash
b2c slas idp get <NAME> --tenant-id <TENANT_ID> [--show-secret]

b2c slas idp set ​

Create or update an identity provider for social or third-party shopper login. When the provider exists, only the fields you pass change.

The name must be a supported provider (adfs, apple, auth0, azure, azure_adb2c, cognito, facebook, forgerock, gigya, gigya_social, google, line, okta, ping, salesforce), or default for any other OpenID Connect provider, optionally followed by -<suffix>, for example google-staging. A default provider needs --claim-mapper to tell SLAS which claims hold the shopper's details.

Usage ​

bash
b2c slas idp set <NAME> --tenant-id <TENANT_ID> [FLAGS]

Flags ​

FlagDescription
--idp-client-idClient ID registered with the identity provider
--idp-client-secretClient secret registered with the identity provider
--auth-urlAuthorization endpoint
--token-urlToken endpoint
--token-info-urlToken info (introspection) endpoint
--user-info-urlUser info endpoint
--well-known-urlOpenID Connect discovery URL
--redirect-urlSLAS callback URL. Defaults to https://<short-code>.api.commercecloud.salesforce.com/shopper/auth/v1/idp/callback/<name> for new providers
--scopesScopes (comma-separated)
--login-merge-claimsClaims used to merge logins (comma-separated)
--claim-mapperOIDC claim mappings (comma-separated)
--[no-]preferredMark as the preferred provider
--[no-]client-creds-bodySend client credentials in the request body instead of a header
--[no-]use-well-knownRead endpoints from the well-known URL
--team-id, --key-idApple Sign In team and key IDs
--fileJSON file with provider fields; flags override it
--show-secretInclude the client secret in the output

A new provider needs the client ID and secret, the authorization, token, token info, user info, and well-known URLs, and scopes.

Examples ​

bash
# Create a Google provider
b2c slas idp set google --tenant-id abcd_123 \
  --idp-client-id 1234.apps.googleusercontent.com --idp-client-secret xxx \
  --well-known-url https://accounts.google.com/.well-known/openid-configuration \
  --auth-url https://accounts.google.com/o/oauth2/v2/auth \
  --token-url https://oauth2.googleapis.com/token \
  --token-info-url https://oauth2.googleapis.com/tokeninfo \
  --user-info-url https://www.googleapis.com/oauth2/v3/userinfo \
  --scopes openid,email,profile

# Change scopes only
b2c slas idp set google --tenant-id abcd_123 --scopes openid,email

# Copy a provider definition between tenants
b2c slas idp get google --tenant-id abcd_123 --show-secret --json > google.json
b2c slas idp set google --tenant-id efgh_456 --file google.json

Notes ​

  • --idp-client-id and --idp-client-secret are the provider's credentials. --client-id and --client-secret remain the Account Manager credentials used to call the SLAS Admin API

b2c slas idp delete ​

Delete an identity provider. Shoppers can no longer log in through it. Prompts for confirmation unless --force is given.

Usage ​

bash
b2c slas idp delete <NAME> --tenant-id <TENANT_ID> [--force]

b2c slas shopper logout ​

Log shoppers out of every session. SLAS revokes their refresh tokens and invalidates their access tokens. Shoppers keep their passwords and must log in again. Prompts for confirmation unless --force is given.

Usage ​

bash
b2c slas shopper logout --tenant-id <TENANT_ID> --site-id <SITE_ID> --login-id <LOGIN_ID>[,...] [--force]

Flags ​

FlagDescription
--site-id(Required) Site ID. Alias: --channel-id. Env: SFCC_SITE_ID
--login-idLogin IDs (comma-separated or repeatable)
--fileFile with one login ID per line (- for stdin)
--force, -fSkip the confirmation prompt

Examples ​

bash
b2c slas shopper logout --tenant-id abcd_123 --site-id RefArch --login-id shopper@example.com
b2c slas shopper logout --tenant-id abcd_123 --site-id RefArch --file compromised.txt --force --json

Notes ​

  • Login IDs are sent in batches of 50
  • The command exits with status 1 when any logout fails, for example when the login ID is unknown
  • Blocked under the NO_UPDATE safety level

b2c slas shopper delete ​

Delete all SLAS records of a shopper, for example to fulfill a GDPR data deletion request. This deletes SLAS data only; delete the customer profile in B2C Commerce separately. Prompts for confirmation unless --force is given.

Usage ​

bash
b2c slas shopper delete <CUSTOMERID> --tenant-id <TENANT_ID> [--email <EMAIL>] [--force]

Pass --email to also match records by the shopper's email address.

Examples ​

bash
b2c slas shopper delete abcdKZmKZm1234567890abcd --tenant-id abcd_123 --email shopper@example.com --force