Dear All, The repository I'm working on recently switched from http to https due to their new network security policy where all requests should pass through the proxy server and connection must be HTTPS. With regards to this, the harvesting from this repository stopped working. Originally, this repository was setup with Tomcat only and all the redirects to https was done by the proxy server. With this development, I installed Apache 2.4 as a front end for Tomcat (using this guide: https://wiki.duraspace.org/display/DSPACE/ModJk) and to handle the SSL connection. I also changed the protocol in oai.cfg the dspace.oai.url and bitstream.baseUrl from http to https.
My problem now is that even though with all the changes I made, when I test the harvesting with dspace -g -a https://repository/oai/request -i all in the command line, it is giving me the OAI server could not be reached error. Also, when I test the OAI baseURL in http://re.cs.uct.ac.za/ for validation, it says "Can't connect" and (certificate verify failed). I was told that the proxy they're using is HaProxy and so I requested them to let Apache in the repository server handle the SSL connection. I have a hunch that the proxy server is still handling the SSL connection because I'm having certificate chain issues when I test the repository url in ssllabs even though I have installed the correct certificates in Apache. Could it be possible that the harvesting failed because of this? Also while searching for possible solutions, I encountered this post: http://dspace.2283337.n4.nabble.com/OAI-server-could-not-be-reached-in-DSpace-5-2-tp4677057p4677085.html but since I am using Apache as the front end for Tomcat, am I right to assume that the properties: -Dhttps.proxySet=true -Dhttps.proxyHost=proxy.server -Dhttps.proxyPort=443 in Tomcat and http.proxy.host = ip_proxy and http.proxy.port = port_proxy in dspace.cfg is not applicable in this scenario? I have set up repositories before that is using the https protocol in their OAI baseURL and harvesting from this server is fine but I have no prior experience when it comes to setting up the repository behind a proxy server. I would greatly appreciate any possible solutions regarding this and if there are any configurations I may have missed. I would also appreciate if someone from this list who have experience setting up their repository behind a proxy server particularly with HaProxy can share their thoughts on this. OS: Windows Server 2008 R2 Java: 1.8.0_45 DSpace version: 5.4 Tomcat: 7.0 Apache: Apache/2.4.25 (Win64) mod_jk/1.2.42 OpenSSL/1.0.2k Thanks in advance! -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/22ba1108-f3c4-4943-99c7-3de3ac0be798%40googlegroups.com.
