mitigation for "strange" but common javascript login forms

Hello,

Thank you for contacting us on that matter!

I will consult our engineering team to determine what could be done to work around this issue with the fields that require typing in order to enable the login button. I will get back to you as soon as I have more information.

Best regards,

Hello,

After doing some tests and looking up some older conversations regarding similar issues, two workarounds stood out for this issue where the Submit button is only activated when the username or password field detects actual typing.

The first method would be to use a typing macro to simulate typing on the web page and enable the Submit button. Here are the steps to configure that :

• In the properties of your web entry, go to the Events section
• Go to the After Open tab
• In the Typing macro field, enter a single character of your choice, {BKSP} and then {ENTER}. The result should look like this :

• You may need to adjust the Initial wait to give RDM more time to load the page before executing the macro

Unfortunately, for the Duo page specifically, this method will not work since the login is done in two steps and only one typing macro can be sent after connection. You would need to type manually in the Password field to enable the second Submit button.

This is where the second workaround can prove more helpful. If you launch the Duo website in External mode, you will be able to autofill your credentials using our DWL browser plugin, which does not have the same limitations as the embedded browser has. Using DWL, the Submit button should be enabled as expected when the Username and Password are inserted.

You can download DWL for your browser of choice here :
https://devolutions.net/web-login

And you can configure the External mode for your web session here :


Best regards,

ok, thanks, the external option is not for us, we really want to keep everything inside RDM to not have to deal with dependencies.

but, I tried the macro with DUO, at least the first entry, the username/email should work this way, but it doesn't. the little popup "executing macro" is popping up, but nothing is entered. something seems to happen tho, we think the form field gets the focus, but nothing is typed in.

Hello,

If the macro executes but nothing is sent into the Username field, there are a few things you might want to verify.

Firstly, you must make sure that once the session is launched you don't click on anything else until the macro is executed to make sure the focus stays on the Username field.

Secondly, if the field is still not filled, it's possible that the page does not have enough time to load before the macro executes. If that's the case, increasing the Wait Time in the properties of your After open - Macro tab should solve the problem.


Best regards,

no, this doesn't help, and would be a qirky workaround anyways.

I would like to see some R&D here as browser based portals are a bigger and bigger part in our admin life and I know it's a neverending catch up with these login forms but for the "bigger" ones (google, o365, duo etc.) some extra effort would help a lot. maybe you can get some clous from password managers? the open source bitwarden for example has no problem filling out duosecurity logins on chrome, even the two page form there..

Hello,

I wanted to let you know that I have just opened an improvement ticket for our engineering department regarding your request, to investigate if anything could be done to allow the activation of the submit buttons without having to resort to a typing macro or using the External display mode, since these two options were unsatisfactory for you.

We will let you know when development is made on the ticket.

Best regards,