PDF《Implementing HTTPS in CONTENTdm 6》

s cdm.conf file. The cdm.conf file should contain VirtualHost directives for HTTP and HTTPS instances. CONTENTdm Website: Once you have configured IIS or Apache to use HTTPS for your CONTENTdm Website, the next step is to create the configurations pointing to your site instance'

s SSL certificate files. Due to the use of cURL the Website code needs to be able to locate the certificates. Configuring the Website is handled by a command line PHP script, manageHttps.php, located in the Website installation'

s admin directory: /admin/manageHttps.php -h=on or off -u=the Secure Server URL -s=the Server SSL Certificate path -w=the Website SSL Certificate path To see help information about manageHttps.php, run the following from the /admin directory: ./manageHttps.php -o The following series of commands could be used to enable HTTPS in a CONTENTdm Website that is installed to the same Linux machine as the CONTENTdm Server: ./manageHttps.php Ch=on The Ch=on switch turns on HTTPS in the CONTENTdm code. ./manageHttps.php Cu=your.servercertificatedomain.edu:443 The Cu switch specifies the URL of your HTTPS CONTENTdm Server. It is not necessary to include https:// in the URL. Be sure that the domain specified matches what was used to generate the SSL certificate. The port should always be specified, even if it is the default 443. ./manageHttps.php Cs= /usr/local/ssl/crt/global.crt ./manageHttps.php Cw= /usr/local/ssl/crt/global.crt The Cs and Cw switches specified the path to the Server'

s and Website'

s SSL certificates, respectively. For an installation where Server and Website use the same domain and are distinguished only by port, the certificate can be shared. If the Server is on a different machine from the Website, the Server'

s certificate must be exported and made available to the Website code. In that case, the paths specified in Cs and Cw may not match. Implementing HTTPS in CONTENTdm

6 September 5,

2012 ?

2012 OCLC Page

3 of

7 If you are running your Website on non-standard ports (ports other than

80 for HTTP and

443 for HTTPS) you will need to add provide some additional configurations using manageHttps.php: manageHttps.php Ci=HTTP Website port manageHttps.php Cp=HTTPS Website port Windows servers: The above examples apply to Apache on Linux. A similar set of commands would be used to configure HTTPS in IIS on Windows: manageHttps.php Ch=on manageHttps.php Cu=your.servercertificatedomain.edu:port manageHttps.php Cs= C:\SSL\certs\thawtePrimaryRootCA.crt manageHttps.php Cw= C:\SSL\certs\thawtePrimaryRootCA.crt All file paths should be enclosed in quotes to account for spaces in directories or file names. To be able to use SSL with CONTENTdm on Windows, the PHP installation needs the openSSL module to be enabled. CONTENTdm installations prior to 6.1.4 did not enable this module by default. To enable openSSL, complete the following steps: 1. Locate the php.ini file used by CONTENTdm. By default this would be located at C:\OCLC\CONTENTdm\Content6\common\php533\php.ini 2. Open the file in a text editor. Find the following line and remove the semicolon to uncomment the setting: extension=php_openssl.dll 3. Restart IIS (either manually in the IIS Manager or at the command line using iisreset). Section IV Testing the Setup Once you have completed the above, verify the configuration by doing the following from a browser running on a workstation machine (not the server where CONTENTdm is installed): 1. View the Server'

s CONTENTdm Administration module over HTTPS: https://your.servercertificatedomain.edu:port/cgi-bin/admin/start.exe Log in and verify you see that Start page. 2. View the Website over HTTP: http://your.website.edu:port If logins are enabled, log into the Website. You should be redirected to an HTTPS login page and redirected back to an HTTPS Website if authentication is successful. 3. Log into the Website Configuration Tool: https://your.website.edu/config/ If you try to force access to the Website Configuration Tool over HTTP, you should be redirected to the HTTPS Website instead. Implementing HTTPS in CONTENTdm