SLAS Identity Providers

To support logging in with social media accounts or other federated login systems (Google’s, for example), you must set up an external identity provider (IDP) for SLAS.

When using an IDP, the source of truth for shopper credentials is the external identity system, instead of the B2C Commerce system. Setting up IDPs is optional. You can still use SLAS for implementing login and API access for shoppers whose credentials are stored in the B2C Commerce system as well (not the external IDP).

The following IDPs are supported by SLAS:

  • Auth0
  • Facebook
  • Google
  • Okta
  • Salesforce

You must use one of the strings from the list of supported IDPs for the value of the name property in the --data-raw object that you use in your API requests. You can also append - to the IDP name, followed by any string to create variations. For example, you can use both "name": "Google" and "name": "Google-test", but not "name": "Googletest".

To request support for an IDP that isn’t on the list, post a message on the Trailblazer Community. We try to fulfill requests within two weeks.

We only support IDPs that are compliant with OpenID Connect. We don’t support SAML.

To set up any of the supported IDPs for SLAS, make a request to the idps endpoint of the SLAS Admin API. Make sure that you have set up a client ID with the IDP before making your request.

You can set up more than one IDP for a tenant. For example, you could set up both Google and Facebook as IDPs for the same tenant.

To enable single sign-on, SLAS must be configured as an authentication provider on core Salesforce clouds. For more information, see this course on Trailhead: Set Up Social Sign-On.

Here’s an example request to set up Google as an IDP for SLAS. Don’t forget to replace {{idp_name}} with one of the supported IDP names listed earlier.

The value for redirectUrl in the request follows a different URL format than the endpoint.