Enable vanity URLs with /cf and /welcome prefixes in AEM as a Cloud Service
This article explains how to enable vanity URLs that begin with /cf and /welcome in Adobe Experience Manager as a Cloud Service by updating the configuration.
Description description
Environment
Adobe Experience Manager as a Cloud Service (all environments: development, staging, production)
Issue/symptoms
In Adobe Experience Manager as a Cloud Service, vanity URLs that start with /cf or /welcome may be blocked if these prefixes are included in the parameterOverride.classicUiPaths configuration. This behavior differs from AEM 6.5, where such vanity URLs are allowed by default.
-
Vanity URLs starting with
/cfor/welcomeare inaccessible in Adobe Experience Manager as a Cloud Service. -
These URLs work as expected in AEM 6.5.
-
Example affected URLs:
https://example.com/cf1https://example.com/welcome1
Cause
The presence of /cf and /welcome in the parameterOverride.classicUiPaths configuration blocks vanity URLs with these prefixes. Removing them allows the desired vanity paths to function.
Resolution resolution
Follow the steps below to resolve the issue:
- Identify the environments where you need to enable vanity URLs with
/cfand/welcomeprefixes (such as development, staging, or production). - Access the Adobe Experience Manager as a Cloud Service configuration for each affected environment.
- Locate the
parameterOverride.classicUiPathsconfiguration parameter. - Remove
/cfand/welcomefrom the list of paths inparameterOverride.classicUiPaths. - Save and deploy the updated configuration.
- Validate that vanity URLs starting with
/cfand/welcomeare accessible after deployment.
Note
If deployment pipelines are running, wait for them to complete before applying the configuration changes to avoid deployment conflicts.