From JumpBox Documentation Wiki

Contents 1 How do I change the default SSL behavior? 1.1 Use unique built-in certificate. (It just works.) 1.2 How to undo the changes above 1.3 Use custom certificate. 1.4 How to undo the changes above

How do I change the default SSL behavior?

The standard behavior when you enable SSL on a JumpBox is to post a notification on the non-SSL port 80. This notification simply tells users to access the application using HTTPS and provides a link that they may follow. We have plans to tailor this behavior in a way that makes the most sense for each application. In the meantime, users who desire different behavior can make changes as suggested below.

Use the section below that matches the SSL option and desired behavior.

IMPORTANT NOTE This will only work on SOME of the JumpBoxes. Some applications behave differently in this regard and will work in ONLY either HTTP or HTTPS at any given time. This is a limitation of the application. This is also why the JumpBoxes currently behave as they do, though we have plans on how to improve this on an application by application basis.

Use unique built-in certificate. (It just works.)

• Redirect to SSL - If you want users to be redirected to the same path they requested over HTTP over SSL, ssh to the JumpBox as the admin user and do the following:

mkdir ~/saved && cp /etc/apache2/sites-available/default.auto ~/saved/
wget http://static.jumpbox.com/godber/misc/ssl-redirect/default.auto.redirect
sudo mv default.auto.redirect /etc/apache2/sites-available/default.auto
sudo /etc/init.d/apache2 restart 

• Enable both HTTP and HTTPS - If you want users to be able to access the application over either HTTP or HTTPS, ssh to the JumpBox as the admin user and do the following:

mkdir ~/saved && cp /etc/apache2/sites-available/default.auto ~/saved/
wget http://static.jumpbox.com/godber/misc/ssl-redirect/default.auto.both
sudo mv default.auto.both /etc/apache2/sites-available/default.auto
sudo /etc/init.d/apache2 restart

How to undo the changes above

If something goes wrong and this change does not appear to work correctly you can undo this change by sshing to the JumpBox as the admin user and do the following:

sudo mv ~/saved/default.auto /etc/apache2/sites-available/default.auto
sudo /etc/init.d/apache2 restart

Use custom certificate.

• Redirect to SSL - If you want users to be redirected to the same path they requested over HTTP over SSL, ssh to the JumpBox as the admin user and do the following:

mkdir ~/saved && cp /etc/apache2/sites-available/default.custom ~/saved/
wget http://static.jumpbox.com/godber/misc/ssl-redirect/default.custom.redirect
sudo mv default.custom.redirect /etc/apache2/sites-available/default.custom
sudo /etc/init.d/apache2 restart 

• Enable both HTTP and HTTPS - If you want users to be able to access the application over either HTTP or HTTPS, ssh to the JumpBox as the admin user and do the following:

mkdir ~/saved && cp /etc/apache2/sites-available/default.custom ~/saved/
wget http://static.jumpbox.com/godber/misc/ssl-redirect/default.custom.both
sudo mv default.custom.both /etc/apache2/sites-available/default.custom
sudo /etc/init.d/apache2 restart

How to undo the changes above

If something goes wrong and this change does not appear to work correctly you can undo this change by sshing to the JumpBox as the admin user and do the following:

sudo mv ~/saved/default.custom /etc/apache2/sites-available/default.custom
sudo /etc/init.d/apache2 restart

Tested The instructions on this page have been tested on the Glpi JumpBox version 1.1.9 by a JumpBox Engineer and are confirmed to work. (details)