<?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 USER-ID API Ip Address not known at start in Automation/API Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/user-id-api-ip-address-not-known-at-start/m-p/30405#M762</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have set up my freeradius system to pass XML updates to the user ID agent. however I have found that with my Juniper wireless system, at the point of the RADIUS "start" accounting message, it doesn't know the users IP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My guess is that once the IP address is allocated it will sent an accounting update with the correct details, so I am hoping we can just add another condition to the PERL script to look for update messages and send those as if they were START messages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However I haven't tried this yet and I was thinking someone may have come across this in the past so would be interested to hear if anyone has hit this, if I am right and whether my solution is correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;David Rickard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 10 Jan 2013 18:29:30 GMT</pubDate>
    <dc:creator>djr</dc:creator>
    <dc:date>2013-01-10T18:29:30Z</dc:date>
    <item>
      <title>USER-ID API Ip Address not known at start</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/user-id-api-ip-address-not-known-at-start/m-p/30405#M762</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have set up my freeradius system to pass XML updates to the user ID agent. however I have found that with my Juniper wireless system, at the point of the RADIUS "start" accounting message, it doesn't know the users IP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My guess is that once the IP address is allocated it will sent an accounting update with the correct details, so I am hoping we can just add another condition to the PERL script to look for update messages and send those as if they were START messages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However I haven't tried this yet and I was thinking someone may have come across this in the past so would be interested to hear if anyone has hit this, if I am right and whether my solution is correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;David Rickard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2013 18:29:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/user-id-api-ip-address-not-known-at-start/m-p/30405#M762</guid>
      <dc:creator>djr</dc:creator>
      <dc:date>2013-01-10T18:29:30Z</dc:date>
    </item>
  </channel>
</rss>

