Difference between revisions of "HTTPS"
Line 36: | Line 36: | ||
For a production system, you would need to provide the relevant certificates and tweak the mod_ssl config accordingly - see: | For a production system, you would need to provide the relevant certificates and tweak the mod_ssl config accordingly - see: | ||
− | * [http://httpd.apache.org/docs/2.2/mod/mod_ssl.html | + | * [http://httpd.apache.org/docs/2.2/mod/mod_ssl.html Apache Module mod_ssl] |
− | * [http://www.modssl.org/docs/2.8/ssl_faq.html | + | * [http://www.modssl.org/docs/2.8/ssl_faq.html mod_ssl FAQ] |
Create a <tt>server.key</tt> on the EPrints server (remembering the passphrase you enter): | Create a <tt>server.key</tt> on the EPrints server (remembering the passphrase you enter): | ||
Line 81: | Line 81: | ||
− | (see ) | + | (see http://www.modssl.org/docs/2.8/ssl_faq.html#remove-passphrase) |
==Create Template for Secure Pages== | ==Create Template for Secure Pages== |
Revision as of 09:50, 25 April 2006
Contents
Add HTTPS Settings
For each ARCHIVEID.xml file, fill in the securehost and securepath entries.
Example:
<archive id="demo"> .... <securehost>secure.mydomain.com</securehost> <securepath>/demo</securepath> .... </archive>
The securehost is vhosted on the same server as your EPrints archive(s).
Secure requests will be of the form https://securehost/securepath.
securepath therefore differentiates requests from individual archives.
Generate Secure Config
$ bin/generate_apacheconf
As well as the usual apache configuration files, this will generate an auto-secure.conf file in each archive's cfg directory.
Set up Secure Host
Under Fedora Core 4, run:
$ yum install mod_ssl
This sets up a test SSL server.
Certificates
For a production system, you would need to provide the relevant certificates and tweak the mod_ssl config accordingly - see:
Create a server.key on the EPrints server (remembering the passphrase you enter):
$ openssl genrsa -des3 -out server.key 1024
Create a certificate request:
$ openssl req -new -key server.key -out server.csr
The important thing when answering the questions is the CommonName: if ultimately the secure web address of your EPrints server is https://www.myeprints.com, then the CommonName value to enter is exactly www.myeprints.com.
Send the server.csr file to your Certificate Authority administrator, who should send you back a .cer file.
Copy server.key and the .cer file to the following locations:
/etc/httpd/conf/ssl.key/server.key /etc/httpd/conf/ssl.crt/eprints.cer
Modify /etc/httpd/conf.d/ssl.conf accordingly:
SSLCertificateFile /etc/httpd/conf/ssl.crt/eprints.cer SSLCertificateKeyFile /etc/httpd/conf/ssl.key/server.key
Include EPrints SSL config
Include each auto-secure.conf file generated by EPrints inside the Virtualhost directive.
On FC4, edit /etc/httpd/conf.d/ssl.conf:
<VirtualHost _default_:443> .... Include /opt/eprints2/archives/ARCHIVEID/cfg/auto-secure.conf
</VirtualHost>
If you have set up SSL certificates, you will be asked to enter your passphrase when you restart apache. To override this:
$ cd /etc/httpd/conf/ssl.key/ $ cp server.key server.key.original $ openssl rsa -in server.key.original -out server.key $ chmod 400 server.key
(see http://www.modssl.org/docs/2.8/ssl_faq.html#remove-passphrase)
Create Template for Secure Pages
Make a copy of template-en.xml:
$ cp template-en.xml template-secure-en.xml
In a multi-language archive, you would need to do this for each language-specific template.
It's a good idea to have a visual differentiation between secure and non-secure pages, e.g. edit template-secure-en.xml and add "(SECURE)" to the title of the page.
Some browsers will complain if images/CSS etc. embedded in a secure page are served by the non-secure host. To solve this, add a new entity to ArchiveConfig.pm/sub get_entities:
$entities{https_base_url} = "https://" . $archive->get_conf("securehost") . $archive->get_conf("securepath");
Now replace image/CSS base_urls with https_base_url.