<?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: AppID and Service use in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/appid-and-service-use/m-p/404378#M91890</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Reasons to&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;use&lt;/EM&gt;&lt;SPAN&gt;&amp;nbsp;the&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;service&lt;/EM&gt;&lt;SPAN&gt;.&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;App ID&lt;/EM&gt;&lt;SPAN&gt;&amp;nbsp;helps developers to easily add authentication to their web and mobile apps with few lines of code&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 01 May 2021 14:59:48 GMT</pubDate>
    <dc:creator>jasonsmith</dc:creator>
    <dc:date>2021-05-01T14:59:48Z</dc:date>
    <item>
      <title>AppID and Service use</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/appid-and-service-use/m-p/404190#M91887</link>
      <description>&lt;P&gt;&lt;SPAN&gt;We have found instances where applications were changed in house to use a different port than the default. So we are in discussion as to what is the best approach to create policy rules.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Below are the two policy rules involving AppID is what we believe to best address our situation:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;1. appID with Service set to protocol port that the app is set to use&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2. appID with Service set no protocol port&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We were wanting to just create one policy rule but realize we may have to settle for multiple.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;SPAN&gt;I have been unable to find documentation that discusses the best approach involving the above and just needed to discuss the pros and cons.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Apr 2021 14:06:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/appid-and-service-use/m-p/404190#M91887</guid>
      <dc:creator>terryc</dc:creator>
      <dc:date>2021-04-30T14:06:48Z</dc:date>
    </item>
    <item>
      <title>Re: AppID and Service use</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/appid-and-service-use/m-p/404378#M91890</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Reasons to&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;use&lt;/EM&gt;&lt;SPAN&gt;&amp;nbsp;the&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;service&lt;/EM&gt;&lt;SPAN&gt;.&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;App ID&lt;/EM&gt;&lt;SPAN&gt;&amp;nbsp;helps developers to easily add authentication to their web and mobile apps with few lines of code&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 01 May 2021 14:59:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/appid-and-service-use/m-p/404378#M91890</guid>
      <dc:creator>jasonsmith</dc:creator>
      <dc:date>2021-05-01T14:59:48Z</dc:date>
    </item>
    <item>
      <title>Re: AppID and Service use</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/appid-and-service-use/m-p/404577#M91915</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/55258"&gt;@terryc&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;In these instances I would just create a security rulebase entry with the app-id and a service-object set for the protocol and port you have modified it to. This would be a standalone entry; don't try to combine standard app-id traffic and what you have to customize.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 03 May 2021 18:45:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/appid-and-service-use/m-p/404577#M91915</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2021-05-03T18:45:28Z</dc:date>
    </item>
  </channel>
</rss>

