<?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: FMC external authentication for CLI access to managed devices. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fmc-external-authentication-for-cli-access-to-managed-devices/m-p/4925741#M1104375</link>
    <description>&lt;P&gt;Yes - you must create the accounts in FMC and designate them as having external authentication.&lt;/P&gt;</description>
    <pubDate>Tue, 19 Sep 2023 12:47:53 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2023-09-19T12:47:53Z</dc:date>
    <item>
      <title>FMC external authentication for CLI access to managed devices.</title>
      <link>https://community.cisco.com/t5/network-security/fmc-external-authentication-for-cli-access-to-managed-devices/m-p/4925632#M1104357</link>
      <description>&lt;P&gt;Hi all, I need some confirmation or experience sharing regarding FMC external authentication for CLI access to managed devices.&lt;/P&gt;
&lt;P&gt;It seems that starting from FTD 7.x the only way to get this working is to specify the list of users for CLI access in FMC under Configuration -&amp;gt; Users -&amp;gt; given External Authentication Object -&amp;gt; CLI Access Filter.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the past, I was able to get this working be returning Radius AV pair Service-Type = 6. I still have some FTD 6.6.x devices in the LAB and indeed it is working without specifying anything in the FMC.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I just want to double check with the community if this is by design or I missed something in the documentation.&lt;/P&gt;
&lt;P&gt;Honestly this is weird and it completely beats the principle of single point of policy definition (AAA server).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Sep 2023 09:45:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-external-authentication-for-cli-access-to-managed-devices/m-p/4925632#M1104357</guid>
      <dc:creator>revenant</dc:creator>
      <dc:date>2023-09-19T09:45:32Z</dc:date>
    </item>
    <item>
      <title>Re: FMC external authentication for CLI access to managed devices.</title>
      <link>https://community.cisco.com/t5/network-security/fmc-external-authentication-for-cli-access-to-managed-devices/m-p/4925741#M1104375</link>
      <description>&lt;P&gt;Yes - you must create the accounts in FMC and designate them as having external authentication.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Sep 2023 12:47:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-external-authentication-for-cli-access-to-managed-devices/m-p/4925741#M1104375</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2023-09-19T12:47:53Z</dc:date>
    </item>
    <item>
      <title>Re: FMC external authentication for CLI access to managed devices.</title>
      <link>https://community.cisco.com/t5/network-security/fmc-external-authentication-for-cli-access-to-managed-devices/m-p/4926260#M1104397</link>
      <description>&lt;P&gt;Interesting, that's the only way we got it to work. We started on 6.6.X and without the local usernames it failed.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Sep 2023 20:59:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-external-authentication-for-cli-access-to-managed-devices/m-p/4926260#M1104397</guid>
      <dc:creator>Eric R. Jones</dc:creator>
      <dc:date>2023-09-19T20:59:25Z</dc:date>
    </item>
  </channel>
</rss>

