Cisco ACE 4710 TACACS issues

[umesh_vid1080]

ACE 4710 TACACS issues ,

How to setup user with Admin context access permission  . I have enable the TACACS and it can directly put me in Context mode not in Admin Context mode .

[venkatkr]

HI Umesh,

Its is a shell attribute setting on the ACS box which will allow you to login as Admin. I have attached a doc which will help you with the settings on the ACS as well as the ACE.

Hope it helps.

Thanks
V . K

[umesh_vid1080]

Hi Venkat !

Thank You for your respond , But i m unable to download the .doc , Could you please re-upload the same.

Thanks

Umesh

[venkatkr]

Yeah something wrong. If this does not work, send me your preferred email and i will email it to you directly.

Thanks
V.K

[umesh_vid1080]

Hi Venkat !

send me at up1080@gmail.com

Thanks !

Umesh

[a-elsheerif]

Hi Venkatkr,

Thanks for your valiable responses,but I have the problem that I'm able to log on to the ACE using the ACS account ( ACS version 5.2 ) but with network monitor privelege not admin privelege so I coudn't access the configuration mode. so please give us your advice.

Thanks in advance.

[venkatkr]

HI.

did you have the right attributes set as per the doc i have attached in this discussion ? There is a av attributes needed which governs if its a network monitor or admin.

Let me know

Thank

VK

[m_sayed_4]

Hi,

Very thanks for your reply, but the problem is tht V5 has a total new structure in configuring the authorizaton policies and Identity stores so me and my colleague Adham dunno how to apply the right attributes.and also I'd like to ask you about any link for ACS V5 materials like videos because the guides from cisco website are confusing

Thanks and best regards

[Cesar Roque]

Hi Mohammad,

I have attached a screenshot which displays the location of where you need
to configure the custom shell profile within ACS 5.    It is important to
configure the requirement as "Optional" so that you don't inadvertently
restrict access to IOS devices that that end up using this shell profile.
Once this is created, you will need to bind this shell profile to the
authorization that your user account is matching within ACS.