<?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 Bradford and PA for user ID in Automation/API Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/bradford-and-pa-for-user-id/m-p/25891#M661</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a way Bradford box can be used to talk to PA-500 so that we can have user identification on the PA: something other than MAC or IP?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Sep 2014 01:06:46 GMT</pubDate>
    <dc:creator>vthakur</dc:creator>
    <dc:date>2014-09-11T01:06:46Z</dc:date>
    <item>
      <title>Bradford and PA for user ID</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/bradford-and-pa-for-user-id/m-p/25891#M661</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a way Bradford box can be used to talk to PA-500 so that we can have user identification on the PA: something other than MAC or IP?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Sep 2014 01:06:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/bradford-and-pa-for-user-id/m-p/25891#M661</guid>
      <dc:creator>vthakur</dc:creator>
      <dc:date>2014-09-11T01:06:46Z</dc:date>
    </item>
    <item>
      <title>Re: Bradford and PA for user ID</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/bradford-and-pa-for-user-id/m-p/25892#M662</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Bradford has a doc on how to set it up.&lt;/P&gt;&lt;P&gt;I use it to map wireless users to PAN-User-ID.&lt;/P&gt;&lt;P&gt;Works fine.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Sep 2014 13:56:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/bradford-and-pa-for-user-id/m-p/25892#M662</guid>
      <dc:creator>UA_MC</dc:creator>
      <dc:date>2014-09-11T13:56:45Z</dc:date>
    </item>
    <item>
      <title>Re: Bradford and PA for user ID</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/bradford-and-pa-for-user-id/m-p/25893#M663</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's built right into the Bradford solution.&amp;nbsp; I have a few customers that run it.&amp;nbsp; All that had to be done was populate the IP address of the User-ID agent and its port number.&amp;nbsp; Just be sure that the agent is configured to allow the inbound API call.&amp;nbsp; It's on the same tab as the regular listener port number.&amp;nbsp; There really shouldn't be much to it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2014 17:29:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/bradford-and-pa-for-user-id/m-p/25893#M663</guid>
      <dc:creator>msemaniuk</dc:creator>
      <dc:date>2014-09-26T17:29:50Z</dc:date>
    </item>
  </channel>
</rss>

