How can I configure a friendly URL for accessing Oracle Fusion Cloud Applications?

As the tenancy administrator or Fusion Applications environment administrator, you've a few options for configuring the URL used to access Fusion Applications.

When first provisioning an environment, you can add a custom prefix to the Oracle-owned application domain that's automatically assigned. For example, instead of abcdef.fa.ocs.oraclecloud.com, you can change it to <prefix>-abcdef.fa.ocs.oraclecloud.com, such as vision-abcdef.fa.ocs.oraclecloud.com. See Fusion Application Environment Setup Wizard and To create an environment.

After the environment is provisioned, you can no longer change the application domain, but you can configure a vanity domain. When configuring a vanity domain, you've two options:

Add a custom prefix. You can now configure a vanity domain to change the prefix to something like visionappsnew-abcdef.fa.ocs.oraclecloud.com. See Add a custom prefix to the application domain.
Configure your own custom domain, such as apps.vision.com. See Create the custom domain.

Note:

The application domain is immutable and you must use it for any integrations that are done, for example, using REST APIs and deep links. Don’t use the vanity domain even if it’s configured, because the vanity domain can change.
If you previously configured a vanity domain for the candidate experience in Oracle Recruiting, you must make a minor adjustment to your Oracle Recruiting setup so that the two vanity domains can coexist. See Recruiting Vanity URL Coexistence with Fusion Vanity URL in Oracle Fusion Cloud Recruiting 26B What's New.

For more information, see Understanding Vanity Domains.

Vanity Domain Impact on iFrames and Cross-Origin Communication in Browsers

If your applications contain iFrames, or if you're using window.postMessage to enable cross-origin communication in a browser, such as between an application page and an iFrame embedded within it, you'll need to do some additional configuration after configuring a vanity domain.

Additional iFrame Setup

If you use a custom Fusion Applications page that embeds your company-owned application page through iFrame, your company-owned page might be configured to return something like this, where <canonical-domain-name> is the original application domain:

Content-Security-Policy: frame-ancestors 'self' https://<canonical-domain-name>

After configuring a vanity domain, you must change this to include both domains:

Content-Security-Policy: frame-ancestors 'self' https://<canonical-domain-name> https://<vanity-domain-name>

Additional window.postMessage Setup

To send messages securely in a browser between a Fusion Applications page and your company-owned application page, you might already have this request configured:

window.postMessage(message, 'https://<canonical-domain-name>');

After configuring a vanity domain, you must change this request to include both possible domains:

window.postMessage(message, 'https://<canonical-domain-name>');
window.postMessage(message, 'https://<vanity-domain-name>');

On the receiving side, you might have something like this:

window.addEventListener("message", (event) => {
  if (event.origin !== "http://<canonical-domain-name>") return;
  // …
});

After configuring a vanity domain, you must change this to:

window.addEventListener("message", (event) => {
  if (event.origin !== "http://<vanity-domain-name>"
    && event.origin !== "http://<canonical-domain-name>") return;
  // …
});