<?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: alfresco through a firewall. in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-through-a-firewall/m-p/283458#M236588</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thx. We're just using it as a web based collaboration tool, so I'm guessing 8443 is all that's needed for us (so far at least). Invites will all be contained within the system, so no SMTP going out from the host.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 28 Feb 2013 15:42:48 GMT</pubDate>
    <dc:creator>tman247</dc:creator>
    <dc:date>2013-02-28T15:42:48Z</dc:date>
    <item>
      <title>alfresco through a firewall.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-through-a-firewall/m-p/283454#M236584</link>
      <description>I'm looking to setup an Internet facing Alfresco 4.2c CE server. It will be behind a corporate firewall, so I need to know what are the minimum ports that need to be enabled to allow Alfresco to function. I'll be using SSL by default (so 8443 is a must). Nobody will be mapping drives to it. All auth</description>
      <pubDate>Tue, 26 Feb 2013 17:37:41 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-through-a-firewall/m-p/283454#M236584</guid>
      <dc:creator>tman247</dc:creator>
      <dc:date>2013-02-26T17:37:41Z</dc:date>
    </item>
    <item>
      <title>Re: alfresco through a firewall.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-through-a-firewall/m-p/283455#M236585</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I think this will give you whole idea&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://wiki.alfresco.com/wiki/Port_numbers" rel="nofollow noopener noreferrer"&gt;http://wiki.alfresco.com/wiki/Port_numbers&lt;/A&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Feb 2013 07:36:58 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-through-a-firewall/m-p/283455#M236585</guid>
      <dc:creator>mitpatoliya</dc:creator>
      <dc:date>2013-02-27T07:36:58Z</dc:date>
    </item>
    <item>
      <title>Re: alfresco through a firewall.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-through-a-firewall/m-p/283456#M236586</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks. I had seen that document, but while it tells you *all* the port numbers, it doesn't actually tell you what's actually required, or what the minimum you need for a working solution. Anyway, I've so far just enabled 8443, and this seems to do pretty much everything I've tested so far (which, granted, isn't that much), but I can fully browse the sight, and upload docs.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Feb 2013 11:24:21 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-through-a-firewall/m-p/283456#M236586</guid>
      <dc:creator>tman247</dc:creator>
      <dc:date>2013-02-27T11:24:21Z</dc:date>
    </item>
    <item>
      <title>Re: alfresco through a firewall.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-through-a-firewall/m-p/283457#M236587</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Yes that should be enough if you are just accessing it though the browser.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;As said previously it completely depends on the what are the services you want to use.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Lets say you want to use alfresco as inbound mail server as well&amp;nbsp; you need to open up the port associated with that so its up to your requirement.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Feb 2013 10:21:41 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-through-a-firewall/m-p/283457#M236587</guid>
      <dc:creator>mitpatoliya</dc:creator>
      <dc:date>2013-02-28T10:21:41Z</dc:date>
    </item>
    <item>
      <title>Re: alfresco through a firewall.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-through-a-firewall/m-p/283458#M236588</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thx. We're just using it as a web based collaboration tool, so I'm guessing 8443 is all that's needed for us (so far at least). Invites will all be contained within the system, so no SMTP going out from the host.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Feb 2013 15:42:48 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-through-a-firewall/m-p/283458#M236588</guid>
      <dc:creator>tman247</dc:creator>
      <dc:date>2013-02-28T15:42:48Z</dc:date>
    </item>
  </channel>
</rss>

