<?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: Source User Information from Syslog push to PA in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/source-user-information-from-syslog-push-to-pa/m-p/242282#M69328</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43193"&gt;@clonesheep&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Easiest way would be to configure the User-ID agent as a syslog listener, and then build out a syslog filter to identify a login and logout event. I believe the Aerohive AP v1.0.0 Syslog Parse Profile actually looks like it would work for your login event.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 05 Dec 2018 18:58:43 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2018-12-05T18:58:43Z</dc:date>
    <item>
      <title>Source User Information from Syslog push to PA</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/source-user-information-from-syslog-push-to-pa/m-p/242175#M69313</link>
      <description>&lt;P&gt;Hi we use Aerohive AP and from there i get syslogs at my Kiwi Syslog Server. Like this one:&lt;/P&gt;&lt;P&gt;ah_auth: add new RT sta: MAC=xxxxxxxx, IP=10.100.100.20, hostname=xxxxx, username=xxxxxx on wifi0.7&lt;/P&gt;&lt;P&gt;And now i need this information in the PA because there i only see in the traffic monitor the Source IP Adress from the AP and no Source User.&lt;/P&gt;&lt;P&gt;How can i configure that the PA can take the log information from the kiwi syslog? Or is there an easy way to take the Aerohive Login/logout and device informations to the firewall?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Aerohive and Palo Alto Network have a cooperation...&amp;nbsp;&lt;A title="" href="https://manualzz.com/doc/23623919/aerohive-and-palo-alto-networks" target="_blank"&gt;https://manualzz.com/doc/23623919/aerohive-and-palo-alto-networks&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Dec 2018 10:47:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/source-user-information-from-syslog-push-to-pa/m-p/242175#M69313</guid>
      <dc:creator>clonesheep</dc:creator>
      <dc:date>2018-12-05T10:47:04Z</dc:date>
    </item>
    <item>
      <title>Re: Source User Information from Syslog push to PA</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/source-user-information-from-syslog-push-to-pa/m-p/242282#M69328</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43193"&gt;@clonesheep&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Easiest way would be to configure the User-ID agent as a syslog listener, and then build out a syslog filter to identify a login and logout event. I believe the Aerohive AP v1.0.0 Syslog Parse Profile actually looks like it would work for your login event.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Dec 2018 18:58:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/source-user-information-from-syslog-push-to-pa/m-p/242282#M69328</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2018-12-05T18:58:43Z</dc:date>
    </item>
  </channel>
</rss>

