As part of the Acoustic branding and user experience enhancement updates, IBM-branded domains such as customer-engagement.ibm.com, ibmmarketingcloud.com, digitalexperience.ibm.com, and api.ibm.com were transferred to Acoustic branded domains.
Note: The IBM-branded domain URLs will no longer work starting June 30th.
Customers and partners who have implemented Acoustic APIs or published Content URLs within their applications were notified to update the URLs. URLs need to be updated according to these detailed instructions if you had any applications or pages that reference Content URLs on the ibm.com domain. This included:
- Applications that call Acoustic Content REST API URLs, either for authoring or delivery.
- HTML pages with URLs that reference images or other resources hosted on Acoustic Content.
- Custom UI extensions that are enabled within your applications.
- A Content palette integrated with your application.
You can find the new API URL for your applications, from the Developer > URL information page on the Content user interface.
Note: If you have implemented a custom domain name and use it to call Content APIs or reference resources, those URLs were not required to be changed. Only URLs that include the ibm.com domain needed to be updated.
If you had completed the updates to transfer your URLs to the new Acoustic branded domains and still have URLs that do not work, the following tips may help you troubleshoot the issue.
- Identify any IBM-branded URLs that may have been missed.
To identify any IBM-branded URLs that may still be lingering in your applications:- Open the developer tools from your browser.
- Browse the web pages where Content is accessed.
- Go to the Network tab.
- In the Domain column, scan for any request that may still be using the IBM URLs.
- Update the identified URLs to the new Acoustic URLs.
- Update the API URLs for applications using the Acoustic sample resources.
If you have used our Acoustic samples from Github or used our Acoustic samples resources as a basis for developing your own applications, you must update the source code for the samples with the new acoustic URLs and hostname.- Most of the Acoustic samples have the API URL, Delivery URL, or the hostname set in the sample application source code. You will need to update these URLs and hostname to the new Acoustic URL or hostname.
- The URLs are specified in different ways depending on the sample. Check the readme provided for each sample to help identify where the URL/hostname information is used in the sample. Update all the URLs/hostname identified with the new URL/ hostname information.
- For some of the sample applications, you must build and deploy the application again after you update the source code
- You can find the new URL and hostname information from the Developer > URL information page on the Content user interface.
- Update your security settings to allow the new Acoustic URLs.
If after you have updated the URLs and if you get CORS errors check for the following:- Make sure you add the new Acoustic URL as a trusted domain in the Security settings.
- Go to the Admin > Settings page in your Content user interface.
- Open the Security tab, and add the new
https://content-eu.goacoustic.com
orhttps://content-us.goacoustic.com
domains to the Cross-origin resource sharing field. - Save your changes.
- If you are making unauthenticated REST calls to delivery APIs from JS code, make sure you are not setting
withCredentials
totrue
. ThewithCredentials
value should only be specified for authenticated calls.
- Make sure you add the new Acoustic URL as a trusted domain in the Security settings.