As part of the Authorization profile, do you use a dACL or another option?
Sorry for all these questions. I've had a lot of issues with pushing dACLs as part of the Authorization policy from ISE to the VPN session on the ASA. Everything works, until it doesn't. We have hundereds of daily users connecting to various VPN gateways (ASA) all over and when I enable Authorization from ISE, it causes few of them to experience an "internal error" on their Cisco Secure Client. Even the highest echelons of TAC have been unable to help resolve this issue successfully.
What's rather strange is that the dACL I am sending is simply permit ip any any and even then the issue occurs.
Are you also using hostscan? We are using hostscan and as per TAC hostscan and CoA don't work together due to a bug.
**Message from TAC: Also I would like to point out to this bug that has been found where it is indicated that hostscan and CoA don’t work together which can be our scenario. https://bst.cisco.com/bugsearch/bug/CSCuu55785
**
TAC's solution for us was to stop sending AuthZ profile with a dACL to the ASA, which is what we did but obviously this is pointless.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: