<?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 ACS 5.4 Saving Problem and Shell Profile Problem in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/acs-5-4-saving-problem-and-shell-profile-problem/m-p/2584578#M72550</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We currently have an ACS&amp;nbsp;Version : 5.4.0.46.0a&amp;nbsp;Internal Build ID : B.221.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Issue 1:&lt;/P&gt;&lt;P&gt;When I make changes on the web user interface&amp;nbsp;I noticed that they do&amp;nbsp;not take effect .I always have to reboot the ACS for the changes to take effect.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Issue 2:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have created authorization rules for Tacacs. I have three rules based on three different shell profiles: Privilege level 15,&amp;nbsp;Privilege level 7 and Privilege Level 1. Whenever we try to authenticate it always goes to the default rule which is deny access. Is there a way we can force the three rules to be used?&lt;/P&gt;&lt;P&gt;I have checked the identity stores and the rule are pointing to the correct store.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 05:07:10 GMT</pubDate>
    <dc:creator>Andrew Mathu</dc:creator>
    <dc:date>2019-03-11T05:07:10Z</dc:date>
    <item>
      <title>ACS 5.4 Saving Problem and Shell Profile Problem</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-5-4-saving-problem-and-shell-profile-problem/m-p/2584578#M72550</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We currently have an ACS&amp;nbsp;Version : 5.4.0.46.0a&amp;nbsp;Internal Build ID : B.221.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Issue 1:&lt;/P&gt;&lt;P&gt;When I make changes on the web user interface&amp;nbsp;I noticed that they do&amp;nbsp;not take effect .I always have to reboot the ACS for the changes to take effect.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Issue 2:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have created authorization rules for Tacacs. I have three rules based on three different shell profiles: Privilege level 15,&amp;nbsp;Privilege level 7 and Privilege Level 1. Whenever we try to authenticate it always goes to the default rule which is deny access. Is there a way we can force the three rules to be used?&lt;/P&gt;&lt;P&gt;I have checked the identity stores and the rule are pointing to the correct store.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 05:07:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-5-4-saving-problem-and-shell-profile-problem/m-p/2584578#M72550</guid>
      <dc:creator>Andrew Mathu</dc:creator>
      <dc:date>2019-03-11T05:07:10Z</dc:date>
    </item>
    <item>
      <title>Hi,Issue 1 :please try to</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-5-4-saving-problem-and-shell-profile-problem/m-p/2584579#M72552</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Issue 1 :&lt;BR /&gt;please try to patch 5.4.0.46.6 or the latest patch&lt;/P&gt;&lt;P&gt;Issue 2 :&lt;/P&gt;&lt;P&gt;did you already enabled the rules? ( not monitor only / disabled )&lt;/P&gt;&lt;P&gt;did reboot the ACS will take the rules effect?&lt;/P&gt;&lt;P&gt;if yes, please try to patch it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Oct 2014 01:19:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-5-4-saving-problem-and-shell-profile-problem/m-p/2584579#M72552</guid>
      <dc:creator>alek.gozali</dc:creator>
      <dc:date>2014-10-21T01:19:52Z</dc:date>
    </item>
    <item>
      <title>Hiwe had the same problem</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-5-4-saving-problem-and-shell-profile-problem/m-p/2584580#M72555</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;we had the same problem (issue 2) yesterday and had always to reboot ACS 5.3 whenever we made some changes in the authorization policies (rules did not apply even if the conditions were true).&lt;/P&gt;&lt;P&gt;We then decided to upgrade to ACS 5.6 and now these problems are gone.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Dominic&lt;/P&gt;</description>
      <pubDate>Fri, 07 Nov 2014 09:13:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-5-4-saving-problem-and-shell-profile-problem/m-p/2584580#M72555</guid>
      <dc:creator>Dominic Stalder (old profile)</dc:creator>
      <dc:date>2014-11-07T09:13:49Z</dc:date>
    </item>
    <item>
      <title>Hi, I uploaded the patch and</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-5-4-saving-problem-and-shell-profile-problem/m-p/2584581#M72557</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I uploaded the patch and it seemed to work for a while before the issue recurred.&lt;/P&gt;&lt;P&gt;However the client will be upgrading to version 5.6 which I believe will solve the problem permanently.&lt;/P&gt;&lt;P&gt;Thanks for the assistance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Andrew&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Apr 2015 08:19:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-5-4-saving-problem-and-shell-profile-problem/m-p/2584581#M72557</guid>
      <dc:creator>Andrew Mathu</dc:creator>
      <dc:date>2015-04-24T08:19:28Z</dc:date>
    </item>
  </channel>
</rss>

