b2c-slas

You can configure OAuth scopes for shopper authentication by using the b2c CLI to manage SLAS clients, allowing you to set up custom scopes like c_loyalty for targeted access. This involves creating or updating clients with specific scope parameters.

Creating a SLAS client for a PWA headless storefront requires using the b2c CLI to define appropriate redirect URIs and channel mappings. You execute a client creation command specifying your tenant ID, channels, and redirect URI.

To debug token issues across tenants, you can use the SLAS commands within the b2c CLI to validate client credentials and troubleshoot authentication tokens. This allows you to identify configuration problems without switching contexts.

Yes, you can list and view existing SLAS clients for shopper login management by running the b2c CLI list command with your specific tenant ID. This provides a clear view of all configured authentication clients.

No, you do not need external services beyond the b2c CLI to manage Shopper Login and API Access Service clients. The Skill supports all client management operations directly through the built-in SLAS commands.

You can update or delete SLAS clients when authentication requirements change by executing the respective update or delete commands via the b2c CLI. This ensures your shopper login credentials remain current.