search

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

Support for vanity hostnames? #157

Closed ranveer5289 closed 2 years ago

ranveer5289 commented 2 years ago

It seems the connector has no support for vanity hostnames. We use vanity hostnames www.development.brand.com on our test environments and the OOBO functionality doesn't work with the connector.

The connector uses the demanwandware.net domain to initiate an OOBO session but our aliases have a below entry which causes issues with the OOBO session as the customer service agent is redirected to www.development.brand.com domain with no OOBO session.

    "development-xxxxxx.demandware.net": [
        {
            "host": "www.development.brand.com",
            "path": "/",
            "locale": "en"
        }
    ]

Is this simply a bug or am missing some configuration at our end?

Moreover, it appears that very soon as part of the SOS project SFCC is going to block calls to the demandware.net domain which will impact OCAPI and thus impacting the connector.

jbachelet commented 2 years ago

Hello @ranveer5289,

The demandware.net hostname is used in b2c-crm-sync because you configured it in the .env file. There is no "hardcoded" reference in b2c-crm-sync to these hostnames.

So to change the hostname to the one you are using in your alias file, you basically just have to change the .env configuration. I guess you already did the configuration now, so you can directly change the configs in the core platform: