From e1858011f8f57acce2f6957837647922eba46618 Mon Sep 17 00:00:00 2001
From: Jon Cox <jon.cox@alfresco.com>
Date: Fri, 6 Jul 2007 08:08:58 +0000
Subject: [PATCH] Made linkvalidation able to check HTTPS links with valid
 certs (bad/untrusted certs look like broken links), pretend ftp links aren't
 broken, detect old href schemas, and added low-level feature to drop href
 info on startup in case we ever need a sledgehammer.  Maybe one day I'll
 really validate ftp links, but not now.  Also fixed startup logic that got
 broken earlier (the config file wasn't getting copied in).

git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@6183 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
---
 .../linkvalidation-service-context.xml        | 40 +++++++++++++++++++
 1 file changed, 40 insertions(+)

diff --git a/config/alfresco/linkvalidation-service-context.xml b/config/alfresco/linkvalidation-service-context.xml
index eb7d64cdd5..72018b6a13 100644
--- a/config/alfresco/linkvalidation-service-context.xml
+++ b/config/alfresco/linkvalidation-service-context.xml
@@ -160,5 +160,45 @@
         <property name="remoteConnectTimeout" value="10000"/>
         <property name="localReadTimeout"     value="30000"/>
         <property name="remoteReadTimeout"    value="30000"/>
+
+        <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
+        <!--  Advanced Option:                                              -->
+        <!--                                                                -->
+        <!--    JSSE Security parameters (for validating HTTPS links)       -->
+        <!--                                                                -->
+        <!--    NOTE:                                                       -->
+        <!--                                                                -->
+        <!--    When the following jsse properties below are commented      -->
+        <!--    out the LinkValidationService uses the system's default     -->
+        <!--    cacert file and password.  Typically, there's no need to    -->
+        <!--    change these values, but if you'd like to do so, you can.   -->
+        <!--                                                                -->
+        <!--    The most common case where you'd use a custom trust store   -->
+        <!--    and password is when you want to validate https links for   -->
+        <!--    which the name on the site's cert does not match the host   -->
+        <!--    you're contacting, is invalid, and/or is not trusted.       -->
+        <!--    If you do nothing, such links will appear "broken".         -->
+        <!--    One option would be to modify your default cert at:         -->
+        <!--                                                                -->
+        <!--         Unix:     ${JAVA_HOME}/lib/security/cacerts            -->
+        <!--         Windows:  ${JAVA_HOME}\lib\security\cacerts            -->
+        <!--                                                                -->
+        <!--    However, this is often not particularly desirable.          -->
+        <!--    By allowing you to point at a custom cacert/password,       -->
+        <!--    the configuration options below allow you to validate       -->
+        <!--    what would be otherwise untrusted "broken" https links      -->
+        <!--    without disturbing the system's default cacert file.        -->
+        <!--                                                                -->
+        <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
+        <!--  <property name="jsseTrustStoreFile"      value="...???..."/>  -->
+        <!--  <property name="jsseTrustStorePassword"  value="...???..."/>  -->
+        <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
+        
+        <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
+        <!--  Low-level parameters that typical users should never modify!  -->
+        <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
+        <property name="purgeAllValidationDataOnBootstrap"  value="false"/>
+
     </bean>
+
 </beans>