connymolin

Hello,

Rest assured that this has been on our radar since it was first brought to us. That said, we've found and fixed the issue, and this fix should be available for the upcoming version (2023.2.15)

Regards,

Great news,

Going to make our work days a hell of a lot easier again :)

Thanks!

Best regards,

Conny

Hello Sascha,

Thank you for reaching us on that matter!

We are still working on getting a test environment on our end to investigate this issue.

We will update this thread as soon as we will have an update to provide,

Best regards,

James Lafleur

Hi James,

It's been two months since this answer now and 10 months since I first reported the issue so forgive me for pointing this out in a rather "brute but honest and well meaning way", but wouldn't it be better to focus on fixing stuff that's broken than releasing new features and functions?

Nothing personal, just saying the engineering dept. might need a nudge in the right direction, and to be frank, I doubt this is hard to fix for the devs and would remove alot of unnecessary irritation among alot of Cisco users.

Don't get me wrong here, I do appreciate the community tips and fixes as well, but when it comes to fixing a feature that's been built in and working like a charm since many years (even though relying on a 3rd party app), it should get a higher prio. Just doesn't feel right that loads of Cisco techs out there should have to individually spend hours of troubleshooting to get a somewhat working interim solution, or worse, start looking at different solutions.

So, thank you for your work so far and I know you're trying to get it fixed, but can we get this upvoted/prioritized somehow? :)

Best regards,

Conny

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?

The only workaround I've found so far is to manually launch ASDM, leave the window open and then open the shortcut you want to use in RDM.

Troublesome and really annoying but at least one doesn't have to copy/paste credentials as RDM manages to find the currently active ASDM window (it just can't launch it from RDM).

An escalation of this issue would be greately appreciated.

-- bump --

Any update on this?

Best regards,

Conny

Hello Conny,

Our Engineering Department has confirmed that we do not support ASDM 1.9.5.0 for now. An improvement ticket has been opened with them and they will see what can be done.

We will be in touch as soon as we will have an update to provide on that matter.

Best regards,

Hi James,

Thanks for the confirmation. I really hope they do get the time to squeeze in a fix for it soon as customers are being forced to the new version by Cisco when upgrading ASDM in their firewalls in order to mitigate security issues.

In the meantime, have a great day and looking forward to hearing from you when you have more information to share.

Best regards,

Conny

Hello,

Thank you for contacting us on that matter!

I would like to ask you a few questions to help us try to replicate this issue internally.

• What version of RDM do you currently use?

• What type of data source do you use?

Best regards,

Hi,

First off, terribly sorry that I haven't answered until now. I honestly forgot about the thread.

Running "2022.2.21.0" at the moment and using a MS SQL datasource.

Hi,

Used to have Cisco ASDM 1.9(2) and it has worked flawlessly with RDM. Now I got forced to update to 1.9(5) which is included in the latest recommended ASDM bundle for Cisco ASA firewalls. Now the ASDM app does not even launch when I try to launch it from RDM.

Tested a few things:

Launched ASDM manually without RDM. It works without problems and I can connect so the issue is not with ASDM.

Launched ASDM manually and triggered the RDM connection. RDM can find the window without any issue at all and fill in my login information so there is no problem with RDM finding the "Login title".

The install path of ASDM is unchanged and is installed at its default location.

Tried resetting my settings by renaming RemoteDesktopManager.cfg without success.

If I re-install 1.9(2) I still get forced to update to 1.9(5) as soon as I connect to one of my customers firewalls that have the newer software.

Anyone else experiencing this?

Best regards,

Conny