Captive Portal doesn't work in FMC

[BaboMigo]

Dears, 

I'am using FTD 6.6.1 managed with FMC, i Configured Internal Certificats, Trusted Certificat, add DNS target with the routed interface, configured the Identity Policy, added it to the Access Policy and allowed it.

When now i go the user computer to go to internet, first i dont have the redirection, secundary, when i write the full URl : https://dj-captiveportal.rasdika.dj:885/ , I get this output : The requested URL / was not found on this server.

[BaboMigo]

I didn't give much attention to ISE-PIC, I thought Cisco FTD had abandoned this technology and that active authentication is much more beneficial than passive one. I'm learning this from you. Is it a good solution that's easy to implement in an environment with 100-200 users?

[ahollifield · Accepted solution]

Active auth is ALWAYS better than passive auth.  That being said captive portal sucks.  The best solution is active authentication using 802.1X to ISE and share that context with FMC via pxGrid.  If that is not available for whatever reason I would personally position ISE-PIC as a "good enough" solution before enforcing an annoying captive portal.

[BaboMigo]

.

[BaboMigo]

.

[BaboMigo]

.