How to use EPrints with HTTPS

From EPrints Documentation
Revision as of 15:09, 6 October 2015 by (talk | contribs) (Updated to reflect more recent versions of EPrints)
Jump to: navigation, search
Manual Sections

For information on setting up HTTPS on EPrints versions earlier than 3.0.5 see Https3.

If you are using Debian/Ubuntu see HTTPS for Debian/Ubuntu.

Note: Setting up your Apache Web server is beyond the scope of this document. Please see your operating system documentation and the Apache documentation for assistance in setting up Apache in your environment.


To start setting up your existing archive to work under HTTPS, you must first edit archives/[repoid]/cfg/cfg.d/ Initially it will probably look something like the following which is the basic configuration file after you have run bin/epadmin create to setup your archive. Alternatively you could run bin/epadmin config_core [repoid] that will prompt you for the following information. It is suggested that you make a backup of the file regardless before proceeding.

$c->{host} = '';
$c->{port} = 80;
$c->{aliases} = [];
$c->{securehost} = ;
$c->{secureport} = 443;
$c->{http_root} = undef;

Update the file to define the secure host and modify ports as needed. If your Apache web server is not using the standard ports (80,443) you can adjust the 'port' and 'secureport' parameters in the config file accordingly.

$c->{host} = '';
$c->{port} = 80;
$c->{aliases} = [];
$c->{securehost} = '';
$c->{secureport} = 443;
$c->{http_root} = undef;

These additional settings may (but rarely) come into play are the following for special or for older setups. In general these settings are only used when dealing with keeping settings from earlier versions of the EPrints software where you've migrated the file from originally. These configuration parameters tend to be deprecated.

$c->{securepath} = '/secure';
$c->{https_root} = '/secure';
$c->{http_cgiroot} = '/cgi';
$c->{https_cgiroot} = '/secure/cgi';

Generate the Apache Configuration File for HTTPS

Run bin/generate_apacheconf to generate the secure Apache configuration files and depending upon the version of EPrints you are using, it may copy the default template archives/[repoid]/cfg/lang/en/templates/default.xml to the template used for HTTPS archives/[repoid]/cfg/lang/en/templates/secure.xml. This will also setup the repository configuration file located in the /opt/eprints3/cfg/apache_ssl/ directory named [repoid].conf.

Add the Main Apache Config File to SSL Config

Depending upon the version of EPrints you are running there are a couple files that may be involved. It is recommended to run bin/generate_apacheconf --man or view the source of bin/generate_apacheconf file to understand what file(s) need to be setup. In general you will need to place a line like either of the following inside your Apache SSL Virtual Host declaration (most likely found in /etc/httpd/conf.d/mod_ssl.conf or /etc/httpd/conf.d/ssl.conf). Make sure that these lines are placed inside the <VirtualHost> Apache directive.

Include /opt/eprints3/archives/[repoid]/var/auto-secure.conf


Include /opt/eprints3/cfg/apache_ssl.conf

Restart Apache to pick up the changes to the Apache configuration

Consult your operating system documentation on how to restart service processes but in general you need to run one of the following commands either as root or using sudo:

# /sbin/service httpd restart
# /etc/init.d/apache2 restart


Open your web browser and access your repository via its URL, this should be done over HTTP. When you click to login you should notice that you will be redirected to an HTTPS connection. Note that in general most tasks that require you to login are now redirected to an HTTPS connection otherwise an HTTP request will be used.