ASDM addon unable to find window
Encountered this on a fresh install of RDM and then upgraded an existing install to the latest ASDM Add-on (v2.3.0.0) to verify repeatability, from the changelog it looks like this was introduced in the September 2016 update of the add-on and I've duplicated the behavior on Windows 10 and 8.1:
When using either Locally installed ASDM or Java Web Start, RDM is unable to locate the window to enter credentials into and errors . I've worked around this by unticking the "Force check if window exists before sending credentials" box in Advanced, but this has already resulted in imsplacement of credentials. Would be nice if the normal behavior could be restored.
All Comments (9)
Hello,
The only change in 2.2.0.0 is the addition of the force window checking and 2.3.0.0 added an option to disable that, which is the same behavior as prior to 2.2.0.0.
I'm curious though, what is the window title? There was an issue with how we handle window titles when sending credentials in RDM (not just in this addon) and we will have a fix out in the next RDM build, maybe this will help your issue.
Regards,
Hubert Mireault
Interesting... The reason I honed in on the add-on is because of the upgraded system - it was working as expected on the latest version of RDM until I upgraded the add-on.
The window's title is "Cisco ASDM-IDM Launcher v1.7(0)" and no amount of cajoling of the expected window title in the entry's properties (that I could think to do) could get it to recognize the window
Looking forward to the next build!
This is the same issue we tested against, when certain special characters were used in the window title (in this case, parentheses), it was impossible for RDM to find the window. The next build should definitely help your issue. :)
Regards,
Hubert Mireault
Any update on when the next build will be released?
If you want to try the change out you could download the latest beta version at the bottom of our download page https://remotedesktopmanager.com/Home/Download
The change is not in the current stable release of RDM yet, only in the beta version.
Regards,
Hubert Mireault
So I've installed the beta and still running into the same problem, at the risk of repeating, this was working fine on the latest stable release until I upgraded the ASDM plugin
So I had the same issue, I'm on 12.0.8.0. I saw this thread, updated the add-on to 2.3.0.0, it did not work, unchecked the "Force check if window exists before sending credentials", and now everything works as expected. My window title is "Cisco ASDM-IDM Launcher v1.5(69)".
I'm not sure if this helps in anyway but I'm hoping it contributes a bit to the discussion since the issue is repeatably resolved for me.
@Michael: Could you try what Rumpler has done and uncheck the "force check if window exists before sending credentials" checkbox? Unchecking that option makes the behavior the same as when using the previous version of the add-on.
Regards,
Hubert Mireault
@Hubert - Feature request: If you create the session to start with "Locally installed ASDM" and you aren't using a trusted certificate, a second prompt pops up for "Do you want to continue", window title "Security Warning". Default option is cancel, however if you "shift-tab", "spacebar", it would select "continue" and open the ASDM, removing 1 mouse click.
Totally nitpicking and the session is fine the way it is, but I figured while it was fresh in my mind...