cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC! We will not comment or assist with your TAC case in these forums.
Please see How to Ask the Community for Help for other best practices.

569
Views
0
Helpful
4
Replies
Highlighted
Beginner

ISE tacacs+ command set for all interface-specific subcommands

Hi,


I'd really like to know what the ISE tacacs+ command set is for all interface-specific subcommands. 

 

" Permit interface* " gets me into the interface configuration mode, but nothing within that mode. Is there a one-line command set that will include all subcommands within the interface mode? (wildcard "*" in the argument box didn't work). 

 

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Every command is treated on its own merits regardless of where you are in the configuration.  ISE has no awarness of the fact that you are at the interface section.  If you allow the user to go to the interface section then you need to allow the user to issue commands:

shutdown

switchport access vlan

no shutdown

 

etc.

View solution in original post

4 REPLIES 4
Highlighted
VIP Engager

You should be able to use ISE to validate your command expressions. Under TACACS Command Sets I think what you are looking for is:
Grant = PERMIT; Command = Interface; Arguments = all;
Try that and test accordingly. Lastly, see section 'TACACS+ Command Sets' here: https://www.cisco.com/c/en/us/td/docs/security/ise/2-4/admin_guide/b_ISE_admin_guide_24/m_ise_tacacs_device_admin.html
Highlighted
VIP Mentor

what kind of user rights ?

 

 

BB
*** Rate All Helpful Responses ***
Highlighted

Every command is treated on its own merits regardless of where you are in the configuration.  ISE has no awarness of the fact that you are at the interface section.  If you allow the user to go to the interface section then you need to allow the user to issue commands:

shutdown

switchport access vlan

no shutdown

 

etc.

View solution in original post

Highlighted

Thank you, it appears that you were correct - all commands within a command group that you want some control over need to be individually defined.