I created a new custom shell profile called "ciscowlc"... (I am pretty sure that is just a name & doesn't have to match anything in particular like in ACS 4.x but just to be consistent, that is what I called it)
Under the "Custom Attributes" tab, I created a new custom attribute
To apply this custom attribute, i did the following:
"Access Policies" -> Created a custom policy called "TACACS WLC Administration" -> Service type = "Device Adiministration", Policy Structure: = Identitiy & Authorization. Allowed Protocols = PAP/ASCII, CHAP & MS-CHAPV2
My Identity is pointing to AD
Under Authorization, created a custom Policy with the following settings:
AD:ExternalGroups = "my ad group my user is contained"
Shell Profile: = "ciscowlc" (same as custom shell profile above)
When I look at the the logs for ACS, it shows successful Authentication & Authorization & that I am hitting the correct policy "TACACS WLC Administration"
When I run a "debug aaa tacacs enable" from CLI on the WLC, here is what I receive...
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...