Co-brand inSync Master Management Console URL
Note: This topic is applicable only to Druva's Managed Service Providers (MSPs). For more information about the Managed Service Provider program, contact Druva Sales.
Overview
This topic explains you the procedure to co-brand inSync Management Console URL.
By default, the URL for accessing inSync Management Console is co-branded and available in the format:
https://<your_company_name>.druva.com
where, <your_company_name> is the actual name of your company.
Based on your preference, you can co-brand and change the URL format to the following:
https://cloud.<your_company_name>.com
To co-brand and use this new URL, you must set up and configure the Apache web server.
Set up the Apache web server
Perform the following activities to set up the Apache web server
Install the Apache web server
To install the Apache web server
- Download and install Apache web server v2.2.
Note: You can install any Apache web server version that supports SSL.
- On the Server Information dialog box, in the Network Domain field, type cloud.<your_company_name>.com, where <your_company_name> is the actual name of your company.
Configure the Apache web server
Before you begin
Create a SSL server certificate and place it under the following directory on your Apache Web Server
<Installation Directory>/Apache Software Foundation/Apache2.2/conf/certs
Note: You must create the certs directory manually.
Procedure
To configure the Apache web server
- Open the Apache configuration file, httpd.conf, located at the following location:
<Installation directory>\Apache Software Foundation\Apache2.2\conf
- Enable the following configuration by removing the preceding pound or hash sign (#)
LoadModule ssl_module modules/mod_ssl.so LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_ajp_module modules/mod_proxy_ajp.so LoadModule proxy_balancer_module modules/mod_proxy_balancer.so LoadModule proxy_connect_module modules/mod_proxy_connect.so LoadModule proxy_ftp_module modules/mod_proxy_ftp.so LoadModule proxy_http_module modules/mod_proxy_http.so LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
- Add the following configuration
Listen 443 http <VirtualHost *:443> ServerName cloud.<your_company_name>.com:443 ServerAdmin <Email address of your server administrator> SSLProxyEngine On SSLEngine on SSLProtocol all -SSLv2 -SSLv3 SSLCipherSuite <Cipher Preference Required> SSLCertificateFile <Type the path to your domain name .crt file> SSLCertificateKeyFile <Type the path to your private key file> ProxyPass /https://<your_company_name>.druva.com/ ProxyPassReverse /<your_company_name>.druva.com/ </VirtualHost>
Sample configuration<VirtualHost *:443> ServerName cloud.mycompany.com:443 ServerAdmin ernie.carter@druva.com SSLProxyEngine On SSLEngine on SSLProtocol all -SSLv2 -SSLv3 SSLCertificateFile "C:/Program Files (x86)/Apache Software Foundation/Apache2.2/certs/cloud.apache.com (ernie.carter@druva.com).pem" #SSLCertificateKeyFile <path to private key file> ProxyPass / https://mycompany.druva.com/ ProxyPassReverse / https://mycompany.druva.com/ </VirtualHost>
Test your Apache web server configuration
After you configure the Apache web server to use the URL - cloud.<your company name>.com, follow these steps to verify your configuration,
-
Start the Apache WebService.
-
Open a web browser, and type your domain name, cloud.<your company name>.com.
The URL must redirect you to the link that you specified in the following configuration in httpd.conf:ProxyPass /https://<your_company_name>.druva.com/ ProxyPassReverse /<your_company_name>.druva.com/
The page specified in the ProxyPassReverse is displayed, and the browser URL is displayed as cloud.<your company name>.com.
Note: After you configure Apache web server, submit a request to Druva Support to add your domain to Druva's Google Maps account. This will enable you to use the Google Maps feature integrated within inSync.