<?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: Controlling Google's Hangout app in Automation/API Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/controlling-google-s-hangout-app/m-p/49165#M1108</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Since the original caller was an SE, I went back to the case and messaged him about the added information you have provided.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 Aug 2014 03:24:12 GMT</pubDate>
    <dc:creator>dkillpack</dc:creator>
    <dc:date>2014-08-01T03:24:12Z</dc:date>
    <item>
      <title>Controlling Google's Hangout app</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/controlling-google-s-hangout-app/m-p/49163#M1106</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Has anyone here dealt with Googles hangout app for mobile devices going through the firewall. The customer wants to allow hangout chat but not file-transfer or video calling. The apps sees it as google-talk and under it is gtalk-voice, google-talk-base and gtalk-file-transfer. If we set up the policy for app filtering would the gtalk-file-transfer be masked by ssl or would it still be seen?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am thinking it would be masked so an ssl decrypt policy would need to be employed. However when I enable the ssl decrypt, the device then can not sign into google hangouts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts or help would be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Darrell&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Dec 2013 11:19:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/controlling-google-s-hangout-app/m-p/49163#M1106</guid>
      <dc:creator>dkillpack</dc:creator>
      <dc:date>2013-12-03T11:19:34Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling Google's Hangout app</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/controlling-google-s-hangout-app/m-p/49164#M1107</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Darrell,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I realize this question was posed some time ago, but our google-hangouts app ID was recently update to reflect Google product changes. Are you still having issues?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Jul 2014 20:59:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/controlling-google-s-hangout-app/m-p/49164#M1107</guid>
      <dc:creator>maurisy</dc:creator>
      <dc:date>2014-07-24T20:59:38Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling Google's Hangout app</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/controlling-google-s-hangout-app/m-p/49165#M1108</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Since the original caller was an SE, I went back to the case and messaged him about the added information you have provided.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Aug 2014 03:24:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/controlling-google-s-hangout-app/m-p/49165#M1108</guid>
      <dc:creator>dkillpack</dc:creator>
      <dc:date>2014-08-01T03:24:12Z</dc:date>
    </item>
  </channel>
</rss>

