10-16-2014 02:51 AM - edited 03-10-2019 10:07 PM
Hi,
We currently have an ACS Version : 5.4.0.46.0a Internal Build ID : B.221.
Issue 1:
When I make changes on the web user interface I noticed that they do not take effect .I always have to reboot the ACS for the changes to take effect.
Issue 2:
I have created authorization rules for Tacacs. I have three rules based on three different shell profiles: Privilege level 15, 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?
I have checked the identity stores and the rule are pointing to the correct store.
Solved! Go to Solution.
10-20-2014 06:19 PM
Hi,
Issue 1 :
please try to patch 5.4.0.46.6 or the latest patch
Issue 2 :
did you already enabled the rules? ( not monitor only / disabled )
did reboot the ACS will take the rules effect?
if yes, please try to patch it.
10-20-2014 06:19 PM
Hi,
Issue 1 :
please try to patch 5.4.0.46.6 or the latest patch
Issue 2 :
did you already enabled the rules? ( not monitor only / disabled )
did reboot the ACS will take the rules effect?
if yes, please try to patch it.
04-24-2015 01:19 AM
Hi,
I uploaded the patch and it seemed to work for a while before the issue recurred.
However the client will be upgrading to version 5.6 which I believe will solve the problem permanently.
Thanks for the assistance.
Regards,
Andrew
11-07-2014 01:13 AM
Hi
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).
We then decided to upgrade to ACS 5.6 and now these problems are gone.
Regards
Dominic
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide