05-01-2019 09:40 PM - edited 02-21-2020 09:05 AM
Hi team,
Where can I find ISE component compatibility with FTD which is not included in the below document.
I can see DACL and COA are supported from FTD6.3. But I still not sure if ISE posture solution for FTD anyconnect VPN can work or partially work.
05-02-2019 12:48 AM
that is correct FTD does support CoA since 6.3 , which means you should be able to set this up just as you would on ASA.
See the following guide as example for FTD
This is an older version for Posture setup with ISE but can be used as a guide line for FTD
05-02-2019 07:28 AM
Hi Danny,
The document is about ASA AnyConnect VPN with ISE posture and FTD AnyConnect VPN without ISE posture.
Do you have FTD AnyConnect VPN with ISE posture document? Does FTD support redirect URL to ensure client provisioning working? If so, how to define redirect ACL, which ACL action mean redirect, permit or deny?
05-04-2019 05:17 PM - edited 05-04-2019 05:21 PM
Moving this topic to FirePOWER.
This is actually among New Features in Firepower Device Manager/FTD Version 6.4.0
Support for RADIUS servers and Change of Authorization in remote access VPN. | You can now use RADIUS servers for authenticating, authorizing, and accounting remote access VPN (RA VPN) users. You can also configure Change of Authentication (CoA), also known as dynamic authorization, to alter a user’s authorization after authentication when you use a Cisco ISE RADIUS server. We added attributes to the RADIUS server and server group objects, and made it possible to select a RADIUS server group within an RA VPN connection profile. |
ISE configurations are identical to that for ASA, as Danny pointed out.
As FTD 6.4 released after the most recent ISE releases, it's not yet vetted by ISE teams. Please ask FirePower team for this info.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide