QuestionQ64

VerifiedRemote access VPNs

Why should a network engineer avoid using the default X.509 certificate when deploying clientless SSLVPN on an ASA?

Explanation

The ASA’s default self-signed X.509 certificate is regenerated on every reboot, so its identity changes and clients cannot reliably validate it. A persistent identity certificate signed by a trusted CA avoids certificate-trust warnings and authentication risk for clientless SSL VPN connections. Cisco: Configure Clientless SSL VPN (WebVPN) on the ASA

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!