---
schema_version: "1"
id: 8909adf33f239178bf927ff03fde9214117faf45dc4366d69298c7ffa5147bb3
title: Troubleshoot Passwordless Login
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/commerce-cloud/commerce-api/guides/slas-passwordless-login-troubleshoot.md
canonical_url: https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/slas-passwordless-login-troubleshoot.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 361b1cad731f8a2c0a3a3b665fc1daca4bda418be87945d115ad6e9646e0521b
products:
  - Composable Storefront
  - Salesforce APIs
---
# Troubleshoot Passwordless Login

Review these troubleshooting steps for issues with the Shopper Login and API Access Service (SLAS) passwordless login and email verification features.

## One-time Password Not Delivered (Email Mode)

**Potential causes:**

- You haven’t configured the sender email in SLAS.
- You haven’t verified the sender email address.
- You haven’t set the password action email template in SLAS.

**Suggested solution:** Verify your SLAS email configuration. See [Passwordless Login with Email](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas-passwordless-login-email.html).

## One-time Password Not Delivered (Callback Mode)

**Potential cause:** The `callbackUri` isn’t allowlisted in the SLAS client, or the callback endpoint can’t be reached.

**Suggested solution:** Confirm that the `callbackUri` in `config.server.ts` exactly matches an allowlisted URL in the SLAS client. Don’t use wildcards—the full URL including protocol must match. Verify that your callback endpoint is publicly accessible and returns a successful response.

## One-time Password Has Wrong Number of Digits

**Potential cause:** The `auth.otpLength` value in `config.server.ts` doesn’t match the one-time password (OTP) length configured in your SLAS client. SLAS generates the token at the length set in the client, so a mismatch causes the storefront to expect a different length than what the shopper receives.

**Suggested solution:** Make sure that `auth.otpLength` in `config.server.ts` matches the OTP length set in your SLAS private client configuration. Valid values are `6` and `8`. See [Configure a SLAS Private Client](https://developer.salesforce.com/docs/commerce/b2c-commerce/guide/slas-passwordless-login-email.html#1-configure-a-slas-private-client).

## Passwordless Registration Form Not Shown

**Potential cause:** Your site doesn’t have the **Enable Email Verification** site preference turned on, so the registration page renders the standard password form.

**Suggested solution:** In Business Manager, go to **Merchant Tools \> Site Preferences \> Storefront Login Preferences** and turn on **Enable Email Verification**. Wait up to 5 minutes for changes to reflect in your storefront. When you turn on this preference, passwordless registration becomes the default mode.

## Email Verification Badge or Change Email Button Not Shown

**Potential cause:** Your site doesn’t have the **Enable Email Verification** site preference turned on, or the preference change hasn’t propagated yet.

**Suggested solution:** In Business Manager, go to **Merchant Tools \> Site Preferences \> Storefront Login Preferences** and turn on **Enable Email Verification**. Wait up to 5 minutes for the changes to reflect in your storefront.

## Customer Can’t Log in with Updated Email

**Potential cause:** Your site doesn’t have the **Enable Loginid Updates for SCAPI** feature switch turned on. When this feature is turned off, the B2C Commerce API (SCAPI) accepts email updates but doesn’t sync the change to the shopper's login ID, causing a mismatch between the display email and the credentials used to log in.

**Suggested solution:** Contact support to enable the **Enable Loginid Updates for SCAPI** feature switch.