This topic explains how to secure DriveWorks and serve over HTTPS with an SSL certificate and why multiple domains are not supported.
To avoid encountering authentication issues and to establish a secure connection we recommend serving the applications listed below over HTTPS for public facing networks.
Most browsers block 'cross-site' (across two sites/domains) cookies by default to prevent unwanted and potentially malicious tracking.
As a result of this, session id cookies are not stored when set on one site from another, resulting in persistent authorization errors even with valid credentials.
DriveWorks applications that are accessed from a browser must run over HTTPS.
This applies to the following:
DriveWorks Live can also use HTTPS and SSL (self-signed) on local development networks
An SSL (Secure Sockets Layer) certificate is a digital data file installed on a website's origin server that enables encrypted HTTPS connections and authenticates the site's identity.
SSL certificates are obtained through a website hosting provider, a domain registrar, or a standalone Certificate Authority.
When hosting the Integration Theme using IIS the SSL certificate is applied in the Site settings.
See the SSL certificate option under the step to Add Website in Create the API Endpoint Website in Internet Information Services (IIS) Manager.
When hosting the DriveWorks Live application see Using an SSL Certificate.
Enabling HTTPS and applying an SSL Certificate is done in the Pro Server - Management Console Configuration File.
See the following links for more information.
To create a HTTPS connection when working locally:
Replace the DnsName(s) shown in the example with:
The machine address can be found in the browser address bar (on the machine the certificate is generated for) when Open Browser is selected from the Live task in DriveWorks Live.
Or
Or
This will open up the Microsoft Management Console.
Click Apply, and then OK.
Before the self-signed SSL certificate can be used it needs to be trusted.
The certificate should now be trusted, and can be used for hosting purposes.
If mmc.exe has been closed, restart and add the Certificates Snap-in (step B.4 above).
See Integration Theme Settings for information on the User file.
See Configure httpsPfxFilePath and httpsPfxPassphrase in the DriveWorksConfigUser.xml file for information on these settings.
httpsPfxFilePath is the full file path to where the .pfx file was saved.
httpsPfxPassphrase is the password set during export.
Go to Live Settings > URL Settings, and check SSL (Advanced).
If not redirected, change the url to https://
In Chrome, clicking the View site information button next to the URL in the address bar certificate should show the certificate is valid.
Other browsers may display a padlock button with the same information.
Any connections to your local server (for example through LiveIntegrationClient.min.js) will now be secured.
Multiple domains or split DNS are not supported when using the following:
Multiple domains are where many domains resolve to a single IP address in the DNS record.
For example:
| domain | IP | |
|---|---|---|
| www.company.org | resolves to | 00.111.2.333 |
| www.company.com | resolves to | 00.111.2.333 |
Similarly, a split DNS (also known as split-horizon or split-view DNS) is where the same domain name resolves to different IP addresses depending on whether the request comes from inside or outside the network.
Certain features of DriveWorks technology require fully qualified domain names (FQDN) in responses and outbound communications.
As such having multiple domains directed to the same IP address or using a Split DNS are not supported.
Each domain name must use its own instance of the applications listed above.
DriveWorks Live - Web Theme
The above does not apply to the Web Theme, however we do recommend using the Integration Theme for its many advantages.
As the Web Theme is typically embedded into third party sites using an iFrame it has a dedicated URL therefore any paths are always relative to the root domain.