What it takes
- The
emailscope. Shopify and Wix use the email address as the key of the customer or site member account, so the platform needs theemailclaim. Allowemailin the client’sAllowedScopesand makeemailrequired (RequireEmailof the client entry). Where the channel does not provide the address, Veriqa asks for it and confirms it by email inside the same sign-in — see Getting the phone number and email. What each channel provides on its own is in the channel catalog. - A public HTTPS address for Veriqa with a valid certificate. The platform calls discovery, token and userinfo from its own servers, so a local test setup will not do.
- The SSO settings on the platform side: a
Client ID, aClient Secretand Veriqa’s discovery address. The platform generates the callback URL itself — add it to the client’s allowed redirect URIs.
Shopify
The feature is called “connect your own identity provider to customer accounts” and runs over OIDC. Shopify lists its requirements for an external provider in the documentation of this feature; compare them with what Veriqa provides (checked with a full authorization code flow):Shopify also has other mechanisms (Multipass, the Storefront API token flow). Veriqa connects
through the external identity provider feature described above; for the status of the other
mechanisms, see Shopify’s documentation.
Wix
Wix accepts an external provider over OIDC as well, and also without a plugin: its SSO settings take aClient ID, a Client Secret and a Config URL — Veriqa’s discovery address — and the
platform pulls the rest itself.
Field mapping in Wix is configurable. If site members are identified by their email address,
request the email scope just as for Shopify.