Using Custom Domains with Web Applications Accessible via Luminate

book

Article ID: 174926

calendar_today

Updated On:

Products

Secure Access Cloud

Issue/Introduction

Using Custom Domains with Web Applications Accessible via Luminate

Resolution

Background:

The custom domain feature allows you to define a DNS name for a specific web application to under any domain address, instead of using the .tenant.luminatesec.com suffix.

 

When using the custom domain capability all SSL certificate management is performed by Luminate and no SSL certificate generation or sharing of private keys is required for any existing certificate you may have.

 

Important: The DNS name which is used must be resolved externally using an internet-based DNS server.

 

The name must be externally resolvable in order for Luminate to validate the validity of the name, successfully create the application and successfully generate an SSL certificate for the application.

 

Process:

The following steps are required in order to define a custom domain for your web application:

  1. Create a new web application (it is not possible to change an application’s DNS name once the application has been created).
  2. In the new application windows expand the “advanced settings” section.
  3. In the “Custom Domain” enter the DNS name of the application under your internet facing zone (for example jira.myorg.com) and click on the “Generate Records” button.
  4. The information about the CNAME record you’ll need to create will then be displayed as follows:

 

  1. Go to you DNS zone management tool and create a new CNAME record with the custom DNS name (as defined in Luminate) in your DNS server zone.
    1. Use the custom domain prefix (e.g. – jira in our previous example) as the record’s name.
    2. Use the value provided by Luminate in step #4 as the value of the CNAME record.
  2. Return to the Luminate administration portal and click on “Add”.
  3. During the health validation stage Luminate will attempt to resolve the DNS name defined in step #3 and validate the resolution successfully redirects to the Luminate infrastructure (using the CNAME creating in step #5).
    1. The health validation process will fail if the CNAME record is not available and the application will be unavailable until the issue is fixed.

Attachments