- last edited on
I manage a couple of FWSMs and ASAs using ASDM.
Recently I get warnings on some of these devices (but only on some).
The warnings say, that the certificate is not valid and that in a future Java-release ASDM will be blocked for this reason (because of some missing attribute in the JAR file).
I have 2 FWSM one of which brings this warning whereas the other one doesn't. Both use the same versions:
FWSM Firewall Version 4.1(6) <context>
Device Manager Version 6.2(2)F
How do I proceed? I'm not at all keen losing ASDM-connectivity...
Thanks for any suggestions.
Go to Solution.
Here is the thing:
Every single time a FWSM, ASA firewall reloads it will generate a self-signed certificate so you will be prompted every time there is a new one as it's not installed on your PC certificate store.
What to do:
The easy and cheap way
Create a permanent-Self signed certificate on the devices and then when you receive the prompt for the next time save it in your
Rate all of the helpful posts!!!
View solution in original post
I tried the easy and cheap way and it works.
Thanks for your help.
Glad to know that
As a thanks remember to follow my website and also like my facebook page hehe
Rate all of the helpful posts!!! Regards, Jcarvaja Follow me on http://laguiadelnetworking.com
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: