@salesforce/b2c-tooling-sdk / clients / DualBackendConfig
Interface: DualBackendConfig
Defined in: packages/b2c-tooling-sdk/src/clients/dual-backend-factory.ts:33
Common shape of every dual-backend factory's input.
SCAPI coordinates (shortCode/tenantId) and the scope-flexible auth strategy are no longer threaded in separately — they are sourced from the instance via B2CInstance.scapiClientConfig. A backend is "SCAPI-capable" iff that getter returns a value (shortCode + tenantId present, and a stateless OAuth flow that can request the required scopes).
preference is optional: when omitted it falls back to the instance's own B2CInstance.apiBackend (default 'auto'), so callers that already resolved the instance from config don't have to re-plumb the flag.
Properties
instance
instance:
B2CInstance
Defined in: packages/b2c-tooling-sdk/src/clients/dual-backend-factory.ts:35
preference?
optionalpreference:ApiBackendPreference
Defined in: packages/b2c-tooling-sdk/src/clients/dual-backend-factory.ts:34