403 Forbidden is preventing OOBO Customer Authentication from getting an access token

SalesforceCommerceCloud / b2c-crm-sync

... a contemporary perspective on how to integrate B2C Commerce and the Salesforce Customer 360 Platform to power frictionless customer experiences in the B2C domain.

https://salesforcecommercecloud.github.io/b2c-crm-sync/

BSD 3-Clause "New" or "Revised" License

65 stars 45 forks source link

403 Forbidden is preventing OOBO Customer Authentication from getting an access token #203

Closed VALiNTRY360 closed 1 year ago

VALiNTRY360 commented 1 year ago

With the recent change that SF made to use eCDN in development and prod, does that require us to generate JWOT tokens? Has anyone else experienced this issue with OOBO?

Unknown

jbachelet commented 1 year ago

Hello,

Thank you for opening the issue. This seems not related to b2c-crm-sync itself, but only tied to the configuration you need to apply. You have to change the domains to match the production/development hostnames so that Salesforce Core is able to authenticate with B2C Commerce.

Closing this issue