Moving from Vanity URL to Custom URLIssue Steps for custom url: 1. Activate the Custom URL Plugin:Enable custom URLs to be set up on your ServiceNow instance. You can activate the Custom URL plugin (com.snc.customurl) if you have the admin role. Before you begin Role required: adminProcedure Navigate to System Definition > Plugins.Find and click the Custom URL plugin.Note: Do not select the Custom URL - Internal plugin, which is an internal component for scripted custom URL APIs.On the Custom URL record, click the Activate/Repair related link.In the Plugin Activation window, click Activate.When the Plugin Activation window reopens with a message that the plugin is activated, click Close & Reload Form to stay on this form.In the Plugin Files related list, find the following property, and change the setting value:Option Descriptionglide.customurl.enabled To enable custom URLs, set the value to True. By default, this property is set to False, which means that you cannot associate a custom URL.Note: To disable this feature, set this property back to False.Click Update. 2.Create a new Custom URL: *IMPORTANT: Must be the same as existing Vanity URL. Add a custom URL to your instance configuration to use instead of your ServiceNow designated URL. Before you begin Role required: adminYou must have purchased or registered a URL before adding the custom URL to your instance. Procedure Navigate to Custom URL.Click New to associate a new domain name.Choose a custom URL to set as your instance. Fill in the appropriate fields:Option DescriptionDomain Name Fully qualified domain name (FQDN) of the custom URL.Note: If the custom URL is 'https://servicenow.acme.com', enter 'servicenow.acme.com' as the FQDN. Is Instance URL Checking this box enables this custom URL for all outbound URLs. Only one active custom URL can be the instance URL. To enable this setting, click the 'Set as Instance URL' button on an active custom URL. This setting activates the chosen custom URL and removes any other custom URL previously set. Status :Status of the custom URL record. Once the status shows as 'Active', the custom URL is provisioned and ready to use.[Optional] Service Portal Choose the service portal to redirect users when they access your instance using the custom URL. A custom URL should activate within six hours. Polling for custom URL job completion occurs every 30 minutes. Note: There is a poll button for manual polling an in-progress custom URL job. 3. When complete let support know so that a change can be completed for System admin team to remove the vanity url. The change record will instruct the Cloud Operations System Administrators team to remove the Vanity URL configuration. This change activity will finalize the transition. Use the Normal change request template [SA] Disable Vanity URL Configuration to create the record. 4. Support will Validate the custom url configuration is in use: Once SA completes the CHG record, use the following command procedure to verify the Custom URL configuration is active on F5 device.On your computer execute the following command. echo | openssl s_client -servername <custom URL> -connect <custom URL>:443 2>/dev/null | openssl x509 -noout -dates -subject –issuer If issuer returned is "Let's Encrypt", it confirms that custom URL config is active. - Example: (internal use only since it shows an actual custom URL); $ echo | openssl s_client -servername example.tech.com.us -connect example.tech.com.us:443 2>/dev/null | openssl x509 -noout -dates -subject -issuernotBefore=Oct 23 22:59:41 2018 GMTnotAfter=Jan 21 22:59:41 2019 GMTsubject= /CN=example.tech.com.usissuer= /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3$