NAC - URL Redirect issues

t3watts33 — Fri, 21 Feb 2020 09:07:27 GMT

I'm testing NAC on a 3000 series concentrator using ACS 4.x. I'm now to the point where I need to test the user experience when someone connects without the CTA agent. We can quarantine them with the downloadable ACL but I need to redirect them to a remediation site. I configured the unknown RAC to use cisco-av-pair | url-redirect=<URL>. When the client lauches a browser they are not redirected (doesnt matter if the home page is set to internal or external). If I type in an internal URL i finally get redirected. Some internal URL's dont redirect and external URL's dont redirect at all. Is anyone else having issues with this? We can see that the RAC attributes for URL redirect are being passed by looking at the logs.

I need the browser to automatically be redirected when launched no matter if the home page is set to internal or external. Of course this wouldnt apply to systems with CTA already installed.

Thanks in advance.

Re: NAC - URL Redirect issues

b.hsu — Fri, 25 Aug 2006 16:42:26 GMT

NAC URL redirect does not occur for hosts that use SOCKS proxy. URL redirect monitors ports 80 and 443 for HTTP connections. SOCKS proxy HTTP connections occur on a different port. As a result, the host is either not redirected or it displays a "Page not found" error.

URL redirect is configured on an ACS server and passed to the VPN 3000 Concentrator during posture validation. You cannot change its settings from the VPN 3000 Concentrator.

topic NAC - URL Redirect issues in Network Security

NAC - URL Redirect issues

Re: NAC - URL Redirect issues