- 22 Aug 2023
- 3 Minutes to read
- Print
- DarkLight
Customized Blackthorn Events Domain
- Updated on 22 Aug 2023
- 3 Minutes to read
- Print
- DarkLight
Blackthorn Events supports custom domains. Currently, we cannot take over a root domain since it has to be forwarded to our service via CNAME.
You can have a subdomain on your main domain with the Event record slugs, such as subdomain.yourdomain.com/event-slug.
For example, the Event Page URL can look like "https://events.yourdomain.com/sample-event" or you can also make it look like "https://www.yourdomain.com/event-slug" (in this case "www" works as a subdomain)
Note: We only set this up for organizations that are already live with our product since there is significant set-up work required.
This includes Sandboxes and any secondary organizations that may be configured.
Here's what we need from you: an available domain and subdomain
Instructions
Contact Blackthorn Support with your domain at least 48 hours before you need to use the custom/migrating domain. Once you receive the CNAME and TXT endpoints, go to Step 3 and complete the process.
DNS Configuration
To enter a vanity domain, complete the following steps.
- Go to the Blackthorn | Events Admin tab.
- Click Settings.
- Enter your “Vanity Domain”.
Submit this information to Blackthorn Support at least 48 hours before you need to use the custom domain.
We will provide you with the CNAME and TXT endpoints for you to update in your DNS records.
If your DNS provider doesn’t allow TXT and CNAME records with the same key, this step will need to be split into two parts. First, you’ll add the TXT records, and then we will generate your SSL Cert. Second, you’ll remove the TXT records, add the CNAME endpoint, and we will generate your SSL Cert.
We will generate your SSL Cert and enable this feature in your org. After this has been completed, please update the following objects and fields to use your customized Event Page URL.
Salesforce Configuration
Note: All communication and email templates should be updated to use these customized URLs.
After the DNS configuration has been completed and the vanity domain is live, please update the following objects and fields to use your customized Event Page URL.
- Event Group: Create a formula text field
Custom Event Group URL
with the following formula on the Event Group object: “domain/” & $Organization.Id & "/g/" & conference360__Key__c - Event: Create a formula text field
Custom Event Page URL
with the following formula on the Event object: SUBSTITUTE(conference360__Event_Page_URL__c , “events.blackthorn.io", "domain") - Attendee: Create a formula text field
Custom AttendeeLink
with the following formula on the Attendee object: SUBSTITUTE(conference360__AttendeeLink__c, “events.blackthorn.io", "domain")
- Event Group: Create a formula text field
Update your Events Domain from Setup > Security > Remote Site Settings > Events_Domain.
- Update 'Remote Site URL' from "https://events.blackthorn.io" to "https://events.YourDomainName.com"
Finally, please make sure to update the Platform Domain field located within Custom Settings > Blackthorn | Events Settings to match the Remote Site URL.
For the SSL text you can use the following:
Cloudflare verifies ownership of each new hostname before a SSL certificate is generated and traffic is allowed to proxy to your vanity domain. The validation mechanism Cloudflare uses for this type of SSL certificate is through the creation of a TXT record. Removing the CNAME record for the vanity domain detaches the SSL from the (sub)domain also. So the control is still guaranteed to be on the domain owner's side.
If you still have questions following the documentation please contact Blackthorn Support. We're happy to help!
RESOURCE: https://www.websitetoolbox.com/support/adding-a-cname-record-127
The reason for the way this is set up is from our Platform as a Service provider, Heroku. Heroku uses an Automated Certificate Management called Server Name Indication. This replaces traditional SSL certificates that require more setup and maintenance.
The validation mechanism Heroku uses for this type of SSL is through the existence of a CNAME record with a specific value pointing to Heroku. Removing that CNAME record detaches the SSL from the (sub)domain also. So the control is still guaranteed to be on the domain owner's side.
We still offer support for traditional Certificate Authority generated SSL certificates. Our customers can purchase their own and supply us a certificate, but this will require continued annual maintenance.