Initial Tenant Creation

Cloud Tenant URLs

The RapidIdentity Cloud solution tenant follows a specific naming convention. You may choose a Vanity URL for your RapidIdentity Cloud tenant should you meet certain technical criteria outlined in this document. Please note that this decision must be made prior to creation of the RapidIdentity Cloud tenant. The creation of your tenant is the first step of the Cloud Deployment process.

RapidIdentity Tenant Naming

By default, RapidIdentity Cloud customer tenant URLs are created with the following naming convention:

• eg: https://springfield.us001-rapididentity.com

You will need to specify the desired hostname.
Alternatively, tenant requests may include a desired hostname as a Vanity URL:

• eg: https://portal.springfield.edu

Vanity URLs

If you prefer a Vanity URL in addition to the default tenant URL, please review the following criteria and confirm your district will be able to support this option:

• The customer must already own the desired domain eg: springfield.edu
• The request must be made in the initial tenant request.
• It is recommended that a new URL is chosen (see additional information below)
• The customer must be able to independently add DNS entries to their Domain via their Domain Control Center to configure the initial DNS resolution.
• Only one (1) Vanity URL can be used per customer tenant.

Vanity URLs Already In Use

While it is recommended that the URL chosen for a Vanity URL is not in use currently, Identity Automation recognizes that consistency for end users is helpful. Should you request a Vanity URL that is already in use:

• You must make Identity Automation aware that the URL is in use with your Vanity URL request
• This request may impact the timing of your Rapid Identity Cloud Portal Go Live
• If needed, you must coordinate with your DNS Provider to configure the Vanity URL with your Portal Go-Live date to avoid down-time for your end users
• You must be available to configure DNS to cut from the existing portal to correctly resolve to the RapidIdentity Cloud Portal in the Portal Go Live window

Additional Clarification

In the case that a Vanity URL is desired, Identity Automation will create an SSL certificate for the customer that supports BOTH the default name (i.e. springfield.us001-rapididentity.com) and the vanity domain (i.e. portal.springfield.edu).

Identity Automation will not own the domain name, rather it must be a URL to a domain that you own. We will, however, own and manage the SSL certificate. Because the certificate references two different domain names (springfield.us001-rapididentity.com and portal.springfield.edu) then both your school and Identity Automation will have to approve its use.

Identity Automation will use DNS validation to renew the SSL certificate on a yearly basis. We will need the correct contact for that domain. This should be the person at your district/university who would be the approver for the SSL certificate on your end (whoever owns the domain).

This decision must be made prior to the creation of the RapidIdentity Cloud tenant and cannot change once the tenant has been created and configuration of the solution has begun.