To set up a whitelabel URL, you'll need the following:
- The domain (that you own/control)
- An SSL certificate
- The Key for the SSL Certificate
- The Root Certificate keychain
The following instructions require some level of IT knowledge as well as access to the domain control panel.
Creating a CSR
To create a CSR, you will need to create both the key and the CSR. On a Unix machine or in Mac OSX's Terminal, you can use the following commands:
- Create a key
openssl genrsa -out <domain_name>.key 2048
- Create a csr
openssl req -new -sha256 -key <domain_name>.key -out <domain_name>.csr
Country Name: The two-letter ISO abbreviation for your country.
State or Province Name: The state or province where your organization is located. Can not be abbreviated.
Locality Name: The city where your organization is located.
Organization Name: The exact legal name of your organization. Do not abbreviate.
Organizational Unit: Optional for additional organizational information.
Common Name (Server Host Name): This is the MOST important. Its the fully qualified domain name you want. You will get a certificate name check warning if this is not an exact match.
Email address: Your email address
Do NOT set a challenge password or "An Optional Company Name"
To get an SSL certificate:
There are lots of providers of certs (RapidSSL, GeoCert, etc.) and they provide tutorials how to do it (for example here is GoDaddy's instructions https://support.godaddy.com/help/article/5269/generating-a-certificate-signing-request-csr-apache-2-x). Recently we have been using www.ssls.com. They have relatively inexpensive PositiveSSL certificate provided by Comodo for $9/year. See https://www.ssls.com/ssl-certificates/comodo-positivessl. When buying a certificate, the provider will need to verify that you are who you say you are. This is usually done by sending an email to the email address setup in DNS (so you will need to have the domain set up in advance).
We need three files total. Please name them accordingly:
- Key - Name Example: app.yourdomain.com.key
- Certificate - Name Example: app.yourdomain.com.cert or .pem
- Root Certificate Keychain - Example: Varies per setup - do not change
There are two ways that you can set up the DNS records so that they direct to the zerista.com site. If you are mapping the root (example.com), please use an A record. If you are using a subdomain (app.example.com), please use a CNAME. This set up should be done through your DNS provider -- generally the same as where you registered the domain, but could be separate. Here is the information for both types of setups:
To set the root (http://www.example.com):
Type: A RECORD
Name: YOUR DOMAIN NAME.com
220.127.116.11 (you need a second instance for this ip)
If the customer is not mapping the root, for example zeristacon.zerista.com, then a CNAME is better, like this:
To set a subdomain (http://app.example.com):
Value: example.zerista.com (the Zerista URL for your conference)
This should be done using the management console provided by the customer's DNS provider. Often times it will also be the same company as their registrar, but does not have to be.
Please note: It can take up to 48 hours for DNS changes to go live.