Cisco ASDM plug-in
I have recently started using RDM, and it's great for organizing shell sessions. I want to integrate ASDM though, and it's not quite as seamless as I'd like. First, my configuration starts locally, waits 3 seconds (6 also worked), tab delays for 300ms, and searches for 'ASDM-IDM'. Under the 'advanced' tab, 'accept certificate before login' is checked.
It looks like this plug-in is basically doing what I could do in about 10 minutes with AutoHotKey:
(or something like that (although this wouldn't have to wait an arbitrary amount of time...)). And that would be fine, if it worked. Instead, it opens a tab in RDM called 'All connections and listening ports" for no apparent reason, opens ASDM twice, and fails to accept the security certificate about half the time.
All of that might be written off as quirky, but acceptable (I have to click a few things out of my way). However, for one of my ASDM sessions, it also fails out with 'unable to launch device manager from <ASA IP>', about half the time (and oddly enough not when it fails to accept the cert). This actually stops the whole thing cold, which is the part that just doesn't work for me.
So can anything be done to fix these issues? I'd love to integrate ASDM launching into RDM, but otherwise I guess I'll just write some AHK scripts...
Thanks!
All Comments (3)
Hi,
We integrate auto hotkey in RDM. Perhaps it your best bet. The problem with ADSM is that we don't have access to an API or a command line. It's a Java application and our interaction is very limited. You could use the variable in the auto hotkey script to open the application. What do you think?
David Hervieux
Yeah, so I already went and wrote a script for AHK which works pretty well. I've attached it.
Currently, it does not obfuscate the username and password, which I honestly don't consider a particularly big deal, because I'm using RDM's embedded script function, so at least they're not stored plaintext. I don't suppose the embedded scripts are stored in an encrypted location? I thought about storing the credentials in a secure repository, and passing them to the AHK script via variable, but the distinction is minor, since the credentials can be stolen with any simple keylogger - or simply by opening a text file in notepad called "ASDM-IDM"...
Also BlockInput doesn't seem to work. I'm not an AHK guru, so I don't know how to fix that. I just don't touch the keyboard for the few seconds it takes to do everything.
My concern now is that macros/scripts/tools for some reason all show up under each session, like so:
It'd be nice to be able to treat an AHK script as a session, and replace the existing ASDM connections in the tree (and also not all show up under each device).
This is off-topic though. I'll keep working on it.
Capture.PNG
ASDM Launcher.ahk
Absolutely right. I will add this to our todo list
David Hervieux