Managing Cisco ACE (Application Control Engine) modules with TACACS+

16 10 2008
This snippet is tested against “recent” Shrubbery tac_plus daemons as of the date of the post. Searching for ACE and TACACS or similar gets confusing because of the RSA ACE server.  Good job Cisco ) Cisco Application Control Engine modules are really separate devices from the “mother” switch, only suckling power and connectivity.  These devices need their own authentication schemes.  It’s pretty easy to turn on TACACS+ authentication and accounting (no authorization again.  Why do vendors insist on only doing 1 or 2 As and not 3?). ACE modules needs a specific optional av-pair in the “exec” service in TACACS+ to authenticate. You can put this in a group or user stanza: 
service = exec {
optional shell:Admin = "Admin default-domain"
}
The format is: shell:<Context> = “<Role> <domain>” I’m not all that into ACE modules yet, so I’ll assume that the reader knows what each of those should be set to in their environment.  For us, we simply want the equivalent of priv-lvl = 15, and that’s what we get above. Note that without that av-pair, the defaults come through as Admin context, default-domain and “Network-Monitoring” role. Also note that excluding the “optional” keyword will render you unable to log in to any IOS devices that use your TACACS+ server for authorization. [ad#footer]
Comments : No Comments »
Categories : ACE, Cisco

Managing ScreenOS firewalls with TACACS+

16 10 2008

This snippet is tested against “recent” Shrubbery tac_plus daemons as of the date of the post.

 

ScreenOS 6.0+ users may have noticed that you can now configure TACACS+ servers to authenticate admin users. I’ll skip over the details, except to say that as of 6.1.0r3, failover isn’t working to either of the backup servers that you can configure, so use with care.
Also note that this is authentication only, no accounting or authorization (except for privilege levels).

ScreenOS needs a specific service in TACACS+ to authenticate. You can put this in a group or user stanza:

service = netscreen {
vsys = root
privilege = read-write
}

The vsys specifies which vsys that user is allowed to. If you only have one, it’s “root”.
privilege can be read-write, read-only or root. As far as I can tell, root allows you to manage local users and mess with nsrp. Otherwise read-write gets most things done. If you’re specifying a non-root vsys, you can also assign vsys-read-write or vsys-read-only as privileges.

[ad#footer]
Comments : 1 Comment »
Categories : Juniper, ScreenOS