weveland

I actually went and created a new executable for launching ASDM. I used autohotkey (AHK2) to make a new Java launcher script. In the sub-folder as the script I placed the latest version of OpenJRE and the latest ASDM launcher.

The AHK launches Open-JRE with the required flags to start ASDM, then I used to have it wait for the appropriate gui elements and fills them in with CLI options passed to it. However I found a better way. I took the AHK script and compiled it into an executable called javaw.exe which ignores all cli options/flags. Now I just use the in-built ASDM plugin, and then point the javaw.exe location to my folder which has my executable in it, and the two sub-folders for open-jre and ASDM. I point the ASDM location to my sub-folder but it doesn't matter as the javaw executable will just ignore the passed flags. The executable launches open-jre which loads the the ASDM .jar file. Then the normal plugin takes over filling in the boxes. I did have to set the plugin delay to 2s because this usually takes just over a second to launch.

This has been the best integration for me with the least amount of reconfiguration, as the new ASDM requires a private key for encryption.

James,

Just pinging for the same issue. Any update on this feature request to upgrade the plugin?

If not, is there an alternative way to handle this instead?