SUNScholar/Secure Internet Connections
For the need to use https, check: https://pressfreedomfoundation.org/encryption-works and https://ssd.eff.org
To check if your internet connection is secure, use: https://www.eff.org/https-everywhere
- 1 Introduction
- 2 Requirements
- 3 Procedure
- 3.1 Step 1 - Create the SSL certificates
- 3.2 Step 2 - Apply for a signed certificate
- 3.3 Step 3 - Get the intermediate CA certs
- 3.4 Step 4 - Configure Tomcat to use the SSL certs
- 3.5 Step 5 - Enable secure XMLUI logins
- 3.6 Step 6 - Enable HTTPS by default
- 3.7 Step 7 - Rebuild DSpace
- 3.8 Step 8 - Check the secure connection
- 4 YouTube Video
- 5 References
- 6 News
This wiki page describes a method of securing communications to a DSpace installation on the internet.
To protect the user credentials of the members of the research community that your repository will serve, it is highly recommended that all logins to the system are encrypted using the procedure detailed below.
- Secure connections are not needed if doing an evaluation of the software on a test server behind your institutions firewall.
- It is assumed that DSpace has been installed according to the suggested guidelines here: http://wiki.lib.sun.ac.za/index.php/SUNScholar/DSpace.
Port 443 Firewall Access
Secure internet connections are created using the secure port (443) which must be opened on the campus and local server firewall.
SSL Certificate Defaults
- The default location for certificates is: /etc/ssl/certs.
- This is where we will put the certificates.
- Other services should point to this folder for the certificates.
Please note: A quiet monopoly has been created in the SSL cert business. Verisign buys Thawte, Verisign buys Geotrust, Symantec buys Verisign.
Update - 2013/10/09. Now we know why a monopoly, so that the NSA can spy on everyone even with SSL certs. What a joke these certs are.
Update - 2016/09/01. Letsencrypt is now allowing us to protect ourselves from the NSA!