<?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: Replacing self-signed certificates with Zentyal-generated certificates in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/replacing-self-signed-certificates-with-zentyal-generated/m-p/275987#M229117</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi David,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I would recommend not to go this way. Instead you should configure an apache in front of tomcat. This is best practice for all our installations and much, much more easy to handle. As a side effect you can harden Alfresco, create redirects and open just the URLs and requests using apache config. Tomcat should be configured to talk only to apache and SOLR.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Anyway you should create new certificates to prevent that everyone can read your content with the default certs who has access to tomcat. For this Alfresco allready provides scripts not to make any mistakes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Of course you can use commercial certs for the tomcat ssl connector but as long you don't understand the complexity in alfresco/SOLR communication and if you're not very familiar with openssl and keystore mechanisms you shouldn't touch this. Otherwise it is very likely that at least your SOLR search will not work any more. So don't go the trappy way if there is an easy and robust one.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 07 Feb 2013 15:55:23 GMT</pubDate>
    <dc:creator>heiko_robert</dc:creator>
    <dc:date>2013-02-07T15:55:23Z</dc:date>
    <item>
      <title>Replacing self-signed certificates with Zentyal-generated certificates</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/replacing-self-signed-certificates-with-zentyal-generated/m-p/275986#M229116</link>
      <description>In order to provide our staff with a consistent experience with each of the servers we run, I'm replacing self-signed certificates with those issued by our Zentyal server, which is acting as the CA. I haven't found entries in either this forum or Zentyal's that deal with this particular topic thorou</description>
      <pubDate>Thu, 07 Feb 2013 13:49:21 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/replacing-self-signed-certificates-with-zentyal-generated/m-p/275986#M229116</guid>
      <dc:creator>dfliddle</dc:creator>
      <dc:date>2013-02-07T13:49:21Z</dc:date>
    </item>
    <item>
      <title>Re: Replacing self-signed certificates with Zentyal-generated certificates</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/replacing-self-signed-certificates-with-zentyal-generated/m-p/275987#M229117</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi David,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I would recommend not to go this way. Instead you should configure an apache in front of tomcat. This is best practice for all our installations and much, much more easy to handle. As a side effect you can harden Alfresco, create redirects and open just the URLs and requests using apache config. Tomcat should be configured to talk only to apache and SOLR.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Anyway you should create new certificates to prevent that everyone can read your content with the default certs who has access to tomcat. For this Alfresco allready provides scripts not to make any mistakes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Of course you can use commercial certs for the tomcat ssl connector but as long you don't understand the complexity in alfresco/SOLR communication and if you're not very familiar with openssl and keystore mechanisms you shouldn't touch this. Otherwise it is very likely that at least your SOLR search will not work any more. So don't go the trappy way if there is an easy and robust one.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Feb 2013 15:55:23 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/replacing-self-signed-certificates-with-zentyal-generated/m-p/275987#M229117</guid>
      <dc:creator>heiko_robert</dc:creator>
      <dc:date>2013-02-07T15:55:23Z</dc:date>
    </item>
    <item>
      <title>Re: Replacing self-signed certificates with Zentyal-generated certificates</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/replacing-self-signed-certificates-with-zentyal-generated/m-p/275988#M229118</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thank you for the reply, Heiko. I have seen many such recommendations for the Apache reverse proxy server, and using this technique could help simplify other services that we run. Do you know if it can handle the Alfresco IMAP component also? I have read of others attempting IMAP funneling with that and Nginx, but it's not always easy to tell how successful or satisfied they were.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Feb 2013 13:58:18 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/replacing-self-signed-certificates-with-zentyal-generated/m-p/275988#M229118</guid>
      <dc:creator>dfliddle</dc:creator>
      <dc:date>2013-02-13T13:58:18Z</dc:date>
    </item>
  </channel>
</rss>

