<?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: TACACS user authentication in WF-500 in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/tacacs-user-authentication-in-wf-500/m-p/431683#M95130</link>
    <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/152936"&gt;@PankajDhobe&lt;/a&gt;&amp;nbsp;for posting this question.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Based on documentation WF-500 supports only RADIUS as an external authentication option, however if you have Panorama in your deployment, you can use TACACS:&amp;nbsp;&lt;A href="https://docs.paloaltonetworks.com/panorama/10-0/panorama-admin/manage-wildfire-appliances/configure-basic-wildfire-appliance-settings-on-panorama/configure-authentication-for-a-wildfire-appliance/configure-tacacs-authentication-for-a-wildfire-appliance.html" target="_blank"&gt;https://docs.paloaltonetworks.com/panorama/10-0/panorama-admin/manage-wildfire-appliances/configure-basic-wildfire-appliance-settings-on-panorama/configure-authentication-for-a-wildfire-appliance/configure-tacacs-authentication-for-a-wildfire-appliance.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind Regards&lt;/P&gt;&lt;P&gt;Pavel&lt;/P&gt;</description>
    <pubDate>Sat, 04 Sep 2021 23:23:59 GMT</pubDate>
    <dc:creator>PavelK</dc:creator>
    <dc:date>2021-09-04T23:23:59Z</dc:date>
    <item>
      <title>TACACS user authentication in WF-500</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/tacacs-user-authentication-in-wf-500/m-p/419839#M93831</link>
      <description>&lt;P&gt;Can we configure TACACS sever profile in WF-500?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So that we will provide TACACS user authentication to login into WF-500.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If it is possible, please share configuration steps or article for the same.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jul 2021 06:14:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/tacacs-user-authentication-in-wf-500/m-p/419839#M93831</guid>
      <dc:creator>PankajDhobe</dc:creator>
      <dc:date>2021-07-16T06:14:47Z</dc:date>
    </item>
    <item>
      <title>Re: TACACS user authentication in WF-500</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/tacacs-user-authentication-in-wf-500/m-p/431683#M95130</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/152936"&gt;@PankajDhobe&lt;/a&gt;&amp;nbsp;for posting this question.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Based on documentation WF-500 supports only RADIUS as an external authentication option, however if you have Panorama in your deployment, you can use TACACS:&amp;nbsp;&lt;A href="https://docs.paloaltonetworks.com/panorama/10-0/panorama-admin/manage-wildfire-appliances/configure-basic-wildfire-appliance-settings-on-panorama/configure-authentication-for-a-wildfire-appliance/configure-tacacs-authentication-for-a-wildfire-appliance.html" target="_blank"&gt;https://docs.paloaltonetworks.com/panorama/10-0/panorama-admin/manage-wildfire-appliances/configure-basic-wildfire-appliance-settings-on-panorama/configure-authentication-for-a-wildfire-appliance/configure-tacacs-authentication-for-a-wildfire-appliance.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind Regards&lt;/P&gt;&lt;P&gt;Pavel&lt;/P&gt;</description>
      <pubDate>Sat, 04 Sep 2021 23:23:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/tacacs-user-authentication-in-wf-500/m-p/431683#M95130</guid>
      <dc:creator>PavelK</dc:creator>
      <dc:date>2021-09-04T23:23:59Z</dc:date>
    </item>
  </channel>
</rss>

