Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
For ASA webvpn we request a certificate from the client which is checked against an internal CA.We have configured revocation-check with protocol ldap and it is working.Certificate has CRL URI:ldap:///CN=xyz.-abc-CA2(4),CN=ABC-CA,CN=CDP,CN=Public%20K...
FPR-2120
ASA Version 9.20(3)7 We have 2 FPR-2120 active/passive failover.Both systems had been registered with smart license about 2 years ago.Multiple failover tests were successfull, last test 2 months ago.Now we had switched off both ASA systems f...
Hello,in ASA Version 9.20(3)7 we tested the new threat-detection servicehttps://www.cisco.com/c/en/us/support/docs/security/secure-firewall-asa/222315-configure-threat-detection-services-for.htmlthreat-detection service invalid-vpn-accessthreat-detec...
We have two ASA in an active/passive failover configurationWhen a failover occurs (by command or by failure of an interface) the http server stops to accept connections from ASDM.We see this message on the console:INFO: Restarting HTTPS server.ERROR:...
@Aref Alsouqi this was just a typo in my post.ldap-defaults DC1.company.internal 636Does not work. In the network trace i see that ASA opens the communication to port 636 but uses protocol ldap (not ldaps).ASA sends bind request with cleartext Userna...
@Rob Ingram In a network trace i see the bind request for CRL retrieval in cleartext.For VPN User Login, LDAPS is used.Configuration:aaa-server abc-intern protocol ldap
reactivation-mode depletion deadtime 1
max-failed-attempts 5
aaa-server abc-int...
Thanks!In the bug document our version 9.20(3)7 is not noted, so i cannot see in which version it is solved.So we have to wait for a further update of the document or to open a tac (what is not easy for us).Joachim