<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to enable an additional certificate ? in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/how-to-enable-an-additional-certificate/m-p/302467#M255597</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Added address="127.0.0.1" in the &amp;lt;Connector port="8443" …&amp;gt; object and the vulnerability applicance can't hit the port anymore.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Nov 2013 16:44:19 GMT</pubDate>
    <dc:creator>ymoisan</dc:creator>
    <dc:date>2013-11-04T16:44:19Z</dc:date>
    <item>
      <title>How to enable an additional certificate ?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/how-to-enable-an-additional-certificate/m-p/302465#M255595</link>
      <description>Hi,We are running a vulnerability testing appliance and we have the following vulnerabilities associated with port 8443/tcp over SSL (Alfresco Tomcat) &lt;IMG id="smileyfrustrated" class="emoticon emoticon-smileyfrustrated" src="https://migration33.stage.lithium.com/i/smilies/16x16_smiley-frustrated.png" alt="Smiley Frustrated" title="Smiley Frustrated" /&gt;SL Certificate - Self-Signed CertificateSSL Certificate - Subject Common Name Does Not Match Server FQDNSSL Certificate - Signature Verification Fa</description>
      <pubDate>Wed, 30 Oct 2013 20:39:48 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/how-to-enable-an-additional-certificate/m-p/302465#M255595</guid>
      <dc:creator>ymoisan</dc:creator>
      <dc:date>2013-10-30T20:39:48Z</dc:date>
    </item>
    <item>
      <title>Re: How to enable an additional certificate ?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/how-to-enable-an-additional-certificate/m-p/302466#M255596</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Ok now I understand the issue is between solr and Alfresco.&amp;nbsp; I don't see instructions on how to create certificates other than self-signed (and with a longer keysize than the default of 1024 used with keytool -genkeypair) and I didn't find a way to have my non self-signed cert to show up in a ssl request, so I'll ask a different question.&amp;nbsp; Since only ports 80 and 443 are open and everything else from the outsie is stopped by a firewall, can I safely dismiss the vulnerabilities found by saying it's internal communications within the Alfresco software stack that is not open to the web ?&amp;nbsp; Our vulnerability testing appliance is in our internal network and that's why it finds port 8443.&amp;nbsp; Am I missing something ?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;TIA&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Oct 2013 14:50:44 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/how-to-enable-an-additional-certificate/m-p/302466#M255596</guid>
      <dc:creator>ymoisan</dc:creator>
      <dc:date>2013-10-31T14:50:44Z</dc:date>
    </item>
    <item>
      <title>Re: How to enable an additional certificate ?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/how-to-enable-an-additional-certificate/m-p/302467#M255597</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Added address="127.0.0.1" in the &amp;lt;Connector port="8443" …&amp;gt; object and the vulnerability applicance can't hit the port anymore.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Nov 2013 16:44:19 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/how-to-enable-an-additional-certificate/m-p/302467#M255597</guid>
      <dc:creator>ymoisan</dc:creator>
      <dc:date>2013-11-04T16:44:19Z</dc:date>
    </item>
  </channel>
</rss>

