Standard Shopper Scope

Grant a client access to a default collection of B2C Commerce endpoints by assigning the preconfigured sfcc.shopper-standard scope. This scope aggregates a commonly required set of over 15 scopes. By reducing the number of scopes assigned to the client, using the sfcc.shopper-standard scope significantly reduces the size of the JSON Web Token (JWT) issued by SLAS.

Configure scopes for a SLAS client by using either the SLAS Admin UI or the SLAS Admin API. To use the SLAS Admin UI, see SLAS Admin UI: Create a SLAS Client. To use the SLAS Admin API, see Advanced: SLAS Admin API.

Before you assign the sfcc.shopper-standard scope, review this table to understand which scopes are and aren't included in the aggregated set. The set of included scopes can't be modified. If you assign sfcc.shopper-standard, the client has access to each scope in the included column.

To add additional scopes beyond those included in sfcc.shopper-standard, append them to the client’s scopes list. For example, this scopes list specifies a client with all the scopes from sfcc.shopper-standard plus sfcc.pwdless_login.

For more information on specific scopes, see Authorization Scopes Catalog.

Don’t use sfcc.shopper-standard if it contains any scopes that you don’t want assigned to the client. It isn’t possible to customize the set of scopes included in sfcc.shopper-standard. Instead, you must explicitly list each scope that you want. For example, here’s the scopes list for a client with all the scopes from sfcc.shopper-standard except for the myaccount scopes.