<?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: Default superuser CLI access via TACACS authentication in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/default-superuser-cli-access-via-tacacs-authentication/m-p/254337#M72179</link>
    <description>&lt;P&gt;Still have not seen how to do this.&amp;nbsp; Has anybody gotten TACACS authentication for CLI access working?&lt;/P&gt;</description>
    <pubDate>Wed, 20 Mar 2019 00:27:51 GMT</pubDate>
    <dc:creator>cdwing</dc:creator>
    <dc:date>2019-03-20T00:27:51Z</dc:date>
    <item>
      <title>Default superuser CLI access via TACACS authentication</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/default-superuser-cli-access-via-tacacs-authentication/m-p/253833#M72065</link>
      <description>&lt;P&gt;Have auth profile setup to use a TACACS server.&amp;nbsp; VSA is passing "superuser" as the admin profile, but it is not giving me access to the CLI as superuser, only GUI.&amp;nbsp; I know I could create another admin profile and grant access that way, but it locks out Admins and Admin Roles from the GUI.&amp;nbsp; Is there anyway to use external auth and get superuser on both GUI and CLI?&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2019 00:56:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/default-superuser-cli-access-via-tacacs-authentication/m-p/253833#M72065</guid>
      <dc:creator>cdwing</dc:creator>
      <dc:date>2019-03-15T00:56:07Z</dc:date>
    </item>
    <item>
      <title>Re: Default superuser CLI access via TACACS authentication</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/default-superuser-cli-access-via-tacacs-authentication/m-p/253930#M72093</link>
      <description>&lt;P&gt;create an admin role that is superuser, then have the VSA reflect the profile name, or create an admin superuser, and set it's authentication profile to tacacs&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2019 14:00:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/default-superuser-cli-access-via-tacacs-authentication/m-p/253930#M72093</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2019-03-15T14:00:51Z</dc:date>
    </item>
    <item>
      <title>Re: Default superuser CLI access via TACACS authentication</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/default-superuser-cli-access-via-tacacs-authentication/m-p/253934#M72096</link>
      <description>&lt;P&gt;When I create a role and give it superuser (Web GUI), it seems to block out the ability to work with admins and admin profiles for that profile.&amp;nbsp; So, they really don't get superuser ability.&amp;nbsp; Would be nice if a VSA existed to pass the CLI attributes (superuser, superreader, etc).&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2019 14:20:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/default-superuser-cli-access-via-tacacs-authentication/m-p/253934#M72096</guid>
      <dc:creator>cdwing</dc:creator>
      <dc:date>2019-03-15T14:20:11Z</dc:date>
    </item>
    <item>
      <title>Re: Default superuser CLI access via TACACS authentication</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/default-superuser-cli-access-via-tacacs-authentication/m-p/254337#M72179</link>
      <description>&lt;P&gt;Still have not seen how to do this.&amp;nbsp; Has anybody gotten TACACS authentication for CLI access working?&lt;/P&gt;</description>
      <pubDate>Wed, 20 Mar 2019 00:27:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/default-superuser-cli-access-via-tacacs-authentication/m-p/254337#M72179</guid>
      <dc:creator>cdwing</dc:creator>
      <dc:date>2019-03-20T00:27:51Z</dc:date>
    </item>
  </channel>
</rss>

