<?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: Securing Alfresco for Access from Public Internet in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/securing-alfresco-for-access-from-public-internet/m-p/308005#M261135</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks will investigate further. I suppose this would still require port 80 etc to be forwarded to Alfresco and hence any URL could be probed. Something I did come across was the possibility of replicating your public content to a&amp;nbsp; staging server in the DMZ and then the risk is greatly reduced. A bit of extra work and cost but sounds much more secure. &lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 06 Mar 2014 21:52:28 GMT</pubDate>
    <dc:creator>mxc</dc:creator>
    <dc:date>2014-03-06T21:52:28Z</dc:date>
    <item>
      <title>Securing Alfresco for Access from Public Internet</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/securing-alfresco-for-access-from-public-internet/m-p/308003#M261133</link>
      <description>Hi all,What is the best practice for exposing an internal alfresco service for external clients/extranet. The server hosts internal documents as well as documents which the public need access too. I am reluctant to expose the whole port tomcat is listening on to the net and thereby allowing people t</description>
      <pubDate>Wed, 05 Mar 2014 21:03:36 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/securing-alfresco-for-access-from-public-internet/m-p/308003#M261133</guid>
      <dc:creator>mxc</dc:creator>
      <dc:date>2014-03-05T21:03:36Z</dc:date>
    </item>
    <item>
      <title>Re: Securing Alfresco for Access from Public Internet</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/securing-alfresco-for-access-from-public-internet/m-p/308004#M261134</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Why don't you just create a public website apart from alfresco and in that webpage post links (public links) to the documents you need the public to have access to. FYI…if you didn't know. Each document is given a public link. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;They get access to those documents without having to log into alfresco.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Mar 2014 23:23:31 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/securing-alfresco-for-access-from-public-internet/m-p/308004#M261134</guid>
      <dc:creator>eswbitto</dc:creator>
      <dc:date>2014-03-05T23:23:31Z</dc:date>
    </item>
    <item>
      <title>Re: Securing Alfresco for Access from Public Internet</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/securing-alfresco-for-access-from-public-internet/m-p/308005#M261135</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks will investigate further. I suppose this would still require port 80 etc to be forwarded to Alfresco and hence any URL could be probed. Something I did come across was the possibility of replicating your public content to a&amp;nbsp; staging server in the DMZ and then the risk is greatly reduced. A bit of extra work and cost but sounds much more secure. &lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Mar 2014 21:52:28 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/securing-alfresco-for-access-from-public-internet/m-p/308005#M261135</guid>
      <dc:creator>mxc</dc:creator>
      <dc:date>2014-03-06T21:52:28Z</dc:date>
    </item>
  </channel>
</rss>

