<?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: ASDM read only using ACS in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/asdm-read-only-using-acs/m-p/4518336#M571648</link>
    <description>&lt;P&gt;CSCvq20174 looks similar to what you are reporting here, but it has been open since 2019.&lt;/P&gt;</description>
    <pubDate>Tue, 14 Dec 2021 03:46:19 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2021-12-14T03:46:19Z</dc:date>
    <item>
      <title>ASDM read only using ACS</title>
      <link>https://community.cisco.com/t5/network-access-control/asdm-read-only-using-acs/m-p/4518144#M571628</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I use to have ACS working fine with ASDM for read only accounts, but it stopped working I believe it might have been a recent ASA upgrade that changed something. I'm running IOS&amp;nbsp;Version 9.14(2)15&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ACS is configured with a shell profile privilege level 5 and command set.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I ran a debug tacacs while trying to login with the read only user on asdm and it looks like asdm is trying to run a "write net" command&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;mk_pkt - type: 0x2, session_id: 484054
mkpkt - authorize user: testro
cmd=write
cmd-arg=net Tacacs packet sent
Sending TACACS Authorization message. Session id: 484054, seq no:1
Received TACACS packet. Session id:1060479447 seq no:2
tacp_procpkt_author: FAIL
TACACS Session finished. Session id: 484054, seq no: 1&lt;/PRE&gt;&lt;P&gt;Cli read only works fine.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why would asdm try to run that command?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas how I can make read only work again with ACS?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Dec 2021 09:44:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/asdm-read-only-using-acs/m-p/4518144#M571628</guid>
      <dc:creator>noliveira</dc:creator>
      <dc:date>2021-12-14T09:44:19Z</dc:date>
    </item>
    <item>
      <title>Re: ASDM read only using ACS</title>
      <link>https://community.cisco.com/t5/network-access-control/asdm-read-only-using-acs/m-p/4518336#M571648</link>
      <description>&lt;P&gt;CSCvq20174 looks similar to what you are reporting here, but it has been open since 2019.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Dec 2021 03:46:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/asdm-read-only-using-acs/m-p/4518336#M571648</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2021-12-14T03:46:19Z</dc:date>
    </item>
  </channel>
</rss>

