To configure custom domain mapping in Fabric Console, you need to first access the Whitelisted Domains pages in Fabric.

1. Log into your Fabric Console.

2. In the left pane, click the API Management tab to display the services tabs, such as APIs, Custom Code, and Custom Data Adapters.
   By default, the Identity service tab is selected under the APIs tab.

3. In APIs > Identity page, click the CONFIGURE DOMAIN.

   

   The Whitelisted Domains page appears.

   

After Step 1: Accessing the Whitelisted Domains Feature, do the following:

1. Click Add Domain. The Fabric Custom URL Configuration dialog appears.

   

   1. In the Fabric Custom URL Configuration, do the following:

      1. In the Fabric identity URL, the field is populated with the installed Fabric identity service URL.
         By default, this is an installed Identity service URL. For example: maa2onpremlx11.temenosgroup.com:8080/authService/100000002

      2. In the Client Facing URL, specify your custom Identity URL. This is a customer-accessible identity URL.

         For example: https://{customdomain}:{customport/authService}

         

   2. In the Runtime Service Mapping, do the following:

      1. In the Fabric Service URL, specify the URL to access the service. This is the original service URL configured in the Fabric console.

      2. In the Client Facing URL, ensure that the $MW_DOMAIN placeholder is specified as the prefix, along with the /services path.
         For example: $MW_DOMAIN/services

         

2. Click Add to save all mappings for the services.
   Once the mappings are saved, the Custom Domains section will be displayed on the page, utilizing the $MW_DOMAIN placeholder.

1. After Step 2: Mapping Fabric URLs to Client Facing URLs is completed, click the Add Custom Domain button that appears on the Whitelisted page > Custom Domains section.

   

   The Custom Domain dialog appears.

   1. In the Namespace, specify the unique name. A logical grouping of Fabric apps that helps manage resources efficiently.

      For example:

      • Temenos.accounts

      

   2. In the Listed Domains, specify the unique name for the domains. You can select multiple domains with comma (,) separated values.

      • For example:

        • temenos.payments.com,payments.temenos.com

2. Click Save.

   NOTE: Your namespaces and domain configurations are saved and can now be accessed for all the apps the same Fabric account, for app design time.

   

Once Step 3: Configuring Custom Domains with Namespaces and Domains is completed, you need to publish a Fabric app with a namespace and domain.

1. Navigate to Apps page Fabric console, and select the application for which you wish to enable custom domain configurations.

2. Navigate to the Publish tab.

3. Click Publish.

   The Publish Confirmation dialog appears.

   NOTE: The Publish Confirmation dialog will be displayed only if you have defined namespaces with domains in Step 3 in this section.

   

4. From the Namespace list, select one of the defined namespaces.

5. From the Domain list, choose the domains for the selected namespace.

6. Click Continue.

   The app is published to the runtime with these domain configurations. You can verify the custom domain mappings in the App Service Document.

After completing Step1 through Step 3 of How to Configure Custom Domain Mapping, you can publish the custom domain configurations by utilizing the MFCLI publish command along with the following parameters:

• -cdns, --customDomainNamespace. Name of the custom domain namespace. Default: <empty string>

• -cdv, --customDomainValue: Name of the custom domain value. Default: <empty string>

• java -jar mfcli.jar publish -u <user> -p <password> -au <Identity URL> -cu <Console URL> 
  -a <app name> [-v <app version>] [--skipwebapp] [--webAppVersion <web binary version>] 
  -e <environment name> [--release-lock] [--incremental] [--skipSwaggerFiles] [--skipEngagementPublish]
   [--publishMicroApps] [--skipPublishedMicroApps] [--snapShotName <snapshot_name>] 
  [-cdns --customDomainNamespace] [-cdv --customDomainValue]

  For example: --customDomainNamespace payments_app1 --customDomainValue payments-domain.com