IF you remove the list profiles option, the users would be falling under the DefaultWebVPN group connection profile. In your case, I think you need to set up 1 Connection profile so that users can fall into that and get a different group-policy based on AD. The steps to do this:
1) Set up a Connection profile say "AnyConnect VPN"
2) Set the group-url to "https://<ASA-fqdn>
3) Disable the list tunnel-group option.
4) Configure your group-policies per AD groups. Also create a Group-policy called "NoAccess" with simultaneous login =0. Assign this as defaul-group-policy for Connection-profile above.
5) Set your Radius Authorization condition to return "OU=<group-policy>" name per AD group. I believe you can also return just "<Group-policy-name".
User experience would be that they only see username and password field when they hit the ASA FQDN. Based on credentials, they will automatically receive group-policy and corresponding permissions set. IF they don't match any conditions specified by Radius, they hit the "NoAccess" group-policy and get denied access.
Where can I find out how to integrate my Cisco products with Threat Response?
There are quick start guides and instructional videos to help you get set up with your Cisco products and the Cisco Threat Response platform.
Inviting all Security & Networking professionals! We want you to tell us what devices you use to do your work and its screen resolution. Your response will help us improve network and security management tools.
Click here to take the 5-minute s...
This guide is intended to show some nifty and powerful use cases that a lot of customers either want or don’t know they want. There are tons of other content out there for specific knobs or capabilities, but this is looking to be a more complete...
Since ASDM 7.12(2) I am no longer able to run ASDM on CentOS 7 using javaws. It appears to launch and dies. However, I am now running ASDM directly in java and it works fine.First attempt "javaws https://<ip of firewall>/admin/public/asd...