<?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: Protecting content pulled via RESTful calls? in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/protecting-content-pulled-via-restful-calls/m-p/238037#M191167</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'm sure the "normal" way to deal with this sort of issue is to put alfresco (and your other infrastructure) behind a firewall so it is not accessable by unauthorised persons.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Or you can proxy just those bits of alfresco that you want to expose.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 09 Aug 2010 17:36:58 GMT</pubDate>
    <dc:creator>mrogers</dc:creator>
    <dc:date>2010-08-09T17:36:58Z</dc:date>
    <item>
      <title>Protecting content pulled via RESTful calls?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/protecting-content-pulled-via-restful-calls/m-p/238036#M191166</link>
      <description>We have a requirement to allow websites to be built by having portions of the pages being pulled from CM via RESTful calls.My concern is that these URLs are visible externally so that people could take them and poke around our content by changing the URL parameters.One solution is to add an encrypte</description>
      <pubDate>Mon, 09 Aug 2010 17:16:38 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/protecting-content-pulled-via-restful-calls/m-p/238036#M191166</guid>
      <dc:creator>rcasazza</dc:creator>
      <dc:date>2010-08-09T17:16:38Z</dc:date>
    </item>
    <item>
      <title>Re: Protecting content pulled via RESTful calls?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/protecting-content-pulled-via-restful-calls/m-p/238037#M191167</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'm sure the "normal" way to deal with this sort of issue is to put alfresco (and your other infrastructure) behind a firewall so it is not accessable by unauthorised persons.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Or you can proxy just those bits of alfresco that you want to expose.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Aug 2010 17:36:58 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/protecting-content-pulled-via-restful-calls/m-p/238037#M191167</guid>
      <dc:creator>mrogers</dc:creator>
      <dc:date>2010-08-09T17:36:58Z</dc:date>
    </item>
  </channel>
</rss>

