Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Info

Valid from Datafari 5.1 (Datafari CE and EE)

Info

Use this only for specific use cases. This option is not recommended.

Datafari is launched by default in HTTPS ie to access to Datafari the url is : https://IP_DATAFARI:443/Datafari

The certificate is autosigned and you can easily replace it by a “real” one. For rare cases, you might want to launch Datafari into HTTP and not HTTPS (you already have a reverse proxy in front of your Datafari installation, you do not have real certificates and you do not want that your users see the warning in their browser about autosigned certificate).

The process is :

  1. Backup the configuration in place for Apache proxy :

    Code Block
    cp /opt/datafari/apache/sites-available/tomcat.conf /opt/datafari/apache/sites-available/tomcat.bkp
  2. Edit the configuration of Apache :

    Code Block
    nano /opt/datafari/apache/sites-available/tomcat.conf
  • Delete the lines related to the VirtualHost 80

Code Block
<VirtualHost *:80>
   ServerName $YOURSERVERNAME
   Redirect / https://YOURSERVER
   CustomLog /dev/null common
   Header set X-Frame-Options SAMEORIGIN

</VirtualHost>
  • Change the line :

Code Block
<VirtualHost *:443>

to :

Code Block
<VirtualHost *:80>
  • Finally remove the lines :

Code Block
SSLEngine on
  SSLCertificateFile /opt/datafari/ssl-keystore/apache/datafari.crt
  SSLCertificateKeyFile /opt/datafari/ssl-keystore/apache/datafari.key

You can save and close the file.

3. Apply the new configuration :

Code Block
apachectl restart

...

Info

Valid from Datafari 4.4 up to Datafari

...

5 for Enterprise Edition

Info

Use this only for specific use cases. This option is not recommended.

Datafari is launched by default in HTTPS ie to access to Datafari the url is : https://IP_DATAFARI:443/Datafari

...

Info

Valid from 4.0 to 4.2 for Enterprise Edition

The documentation below is valid from Datafari v4.0.0 to 4.2

...