RDM Free – automatic Typing Macro for Website

Hello,

Good news on the main question: there is no Free edition limitation here. The Events section — with Before opening / After opening — is available in every edition and for every entry type, including Website. It is simply hidden by default.

The entry editor opens in a simplified view that hides the more advanced sections. Open the entry's properties and click Show all properties at the bottom of the left-hand section list — Events then appears under the Connection group, and After opening → Typing macro is what you want for an automatic login on open.

If you would rather not toggle it, you can move Events into the simplified list permanently under File – Options – User interface – Simplified view.

On your other two points:
HTML autofill only works when the entry opens in the embedded browser. If it is set to open in an external browser, RDM has no access to the page, so both element-based autofill and custom JavaScript are unavailable — only Basic/NTLM-style authentication can be passed. Worth checking first. Two other things can silently disable it: the enforce origin check option, which skips autofill when the page origin does not match the entry's URL (routers that redirect to a different host or port often cause this), and login forms built in JavaScript, where the fields may not exist yet when the fill runs — raising the autofill delay sometimes helps. There is also an alternate autofill engine you can try under File – Options – Types – Web.

Custom JavaScript with a special character in the password — this one looks like a genuine bug on our side, and your observation is the giveaway. The typing macro substitutes $PASSWORD$ literally, but the custom JavaScript path escapes the value for XML first, so a password containing &, < or > is turned into &, < or > before it reaches the page — and the site correctly reports a wrong password.

Could you confirm which special character your password contains? If it is one of those three, that is exactly what you are encountering, and we will get it fixed.

Regards

Hello,

We are using Remote Desktop Manager Free 2026.3.5.0 with a Xiaomi router Website entry.

Configuration:
- Website entry: Mi - Rak
- URL: https://router.miwifi.com
- Embedded browser: Microsoft Edge
- Linked credential: Xiaomi Routers - Credential
- Router IP: 192.168.31.191

Manual login works correctly when the password is typed by hand.

We want automatic login using:
Properties → Connection → Events → After opening → Typing Macro.

We tested separately:

$PASSWORD${ENTER}

$PASSWORD${DELAY}{ENTER}

$PASSWORD$ {BACKSPACE}{DELAY}{ENTER}

We also tested different Initial Wait, Delay and Command timing values.

In every case RDM visibly fills the password field, but Xiaomi returns:
“Password is incorrect”.

Sometimes RDM also stays on:
“Executing macro”.

We tested “Allow password in variable” in both:
- Mi - Rak Website entry
- Xiaomi Routers - Credential

The linked credential contains the correct password and manual login with the same password works.

The password contains a special character.

We previously tested Custom JavaScript as well, but it also produced an incorrect password. David Hervieux mentioned that special characters may be XML-escaped in Custom JavaScript.

Question:

Why does $PASSWORD$ through Typing Macro produce a password that Xiaomi rejects, while manually typing the same stored password works?

Is this a known issue in RDM 2026.3.5.0 with special characters / WebView2?

Please give us the exact supported method for automatically entering a linked credential password in an embedded Edge Website entry.

Thank you.

Hi,
Thank you for the very detailed report — it allowed us to reproduce this quickly. You haven't misconfigured anything; you've found a real bug. In fact, you've found two, which is why both methods you tried failed.

1. Custom JavaScript — $PASSWORD$ is XML-encoded before the script runs, so a password containing &, <, or > arrives at the page as &, <, or >. That confirms what I mentioned to you earlier.

2. Typing macro — the password is substituted into the macro before the macro text is parsed. Any ( ) { } + ^ % or space in the password is then read as macro syntax instead of being typed. That also explains the occasional hang on "Executing macro" — a stray brace from the password leaves the macro parser with an incomplete command.
In both cases, RDM fills the field, which is why it looks correct on screen, but the characters that actually reach Xiaomi differ from your stored password. Both issues are now logged and will be fixed in an upcoming release.

In the meantime, use the Website entry's built-in auto-fill instead of a macro or custom JavaScript. In the entry's properties, under the website/auto-fill settings, set the username and password field IDs — or use the [USERNAME] and [PASSWORD] placeholders to let RDM locate the fields itself, and [ENTER] to submit. That method passes the password to the page without any text escaping in between, so special characters work correctly today. Please leave "Allow password in variable" enabled for the entry.

Sorry for the time you lost on this, and thank you for narrowing it down so precisely — it made the diagnosis much faster.

Regards

RDM Web Login: Special characters in passwords can fail with Typing Macro / Custom JavaScript – working Autofill workaround

Hello,

I ran into a web login issue in Remote Desktop Manager 2026.3.5.0 where a linked credential works when the password is typed manually, but fails when the password is inserted through Typing Macro or Custom JavaScript.

Environment:
- Remote Desktop Manager Free 2026.3.5.0
- Website entry
- Embedded Microsoft Edge / WebView2
- Linked Credential
- Password contains special characters

Observed behavior:
- Manual password entry works correctly
- Typing Macro fills the password field, but authentication fails with “Password is incorrect”
- In some cases RDM remains on “Executing macro”
- Custom JavaScript may also alter passwords containing special characters

Devolutions confirmed that special characters can be affected differently by Typing Macro and Custom JavaScript.

Working workaround:

Use the built-in Website Autofill instead of Typing Macro / Custom JavaScript.

Login → Autofill:
- Autofill login: ON
- Auto-submit: ON
- Only send the password in the HTML password field: ON
- Autofill delay: 2000 ms

Login → HTML control:
- Form ID: blank
- Username ID: blank
- Password ID: actual HTML input ID
- Login button ID: [ENTER]

In my case, Discover could not detect the password field.

Using Edge DevTools Console:

document.querySelectorAll('input[type="password"]')

returned:

input#password.ipt-text

So the working setting was:

Password ID = password

After removing the Form ID and adding a 2000 ms Autofill delay, the password was injected correctly and the login worked.

Important:
- Disable old Typing Macro / After opening actions
- Remove old Custom JavaScript
- Use the real password field ID from DevTools if Discover cannot find it

This may help with dynamically rendered web interfaces where the password field is not available immediately when the page first loads.

Hope this helps others running into the same issue.