02-24-2014 12:57 PM - edited 03-20-2019 08:12 PM
I am running 1.7.0_51_b13 with ADSM 7.1.5(100) and I still have the issue. Bug stiill exists in the hotfix.
05-01-2014 11:35 AM
I was able to solve the issue by adding an externally signed certificate to the ADSM and giving it a host name. If I access it via host name then I no longer get error messages and it works fine.
05-15-2014 12:01 PM
I was able to solve the issue by enrolling and authenticating the ASA with an internal CA, configuring internal DNS to point to the common name used in the cert, and using the hostname in ASDM (similar to harold's solution but using internal issued cert rather than external cert).
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