Macro password and special characters
Hello
I have a password that contains the % symbol in it, which is a special symbol that represents the ALT key in typing macros.
I'm using the following macro: $USERNAME${TAB}$MACRO_PASSWORD${ENTER}
The password starts with the % symbol and the typing macro interprets it as an ALT key modifier instead of typing in the character.
Is there a workaround for this?
Also, the reason I have to create this macro is because I need to add a delay of 5 seconds for the autofill login on an external web browser session. The session uses a self-signed cert and the browser displays a warning about this. The autofill doesn't work in these cases as the user needs to manually proceed past the warning page. This occurs often with routers and other network devices which use self-signed certs. It would be great if we could add a delay on the autofill page or if this cert warning could be detected programmatically for autofill. This is not a problem for embedded sessions as RDM presents a cert warning dialog before loading the website, but some router UI doesn't work 100% in embedded IE like it does in external IE.
All Comments (9)
Hi,
I tried to reproduce the issue with the password and I'm unable. I run the macro in Notepad and I get the %. Would you mind to give me more information about the password by email? I would like to reproduce the sequence
David Hervieux
Hi,
I just created a new data entry with username asdf and password %asdf
My macro is $USERNAME${TAB}$PASSWORD${ENTER}
I used notepad and the result is: asdf{TAB} (then Windows makes the 'ding' sound, same as if I press ALT+%)
If password is asdf% the result is: asdf{TAB}asdf (again ding sound)
If password is &asdf the result is: asdf{TAB}&asdf
If password is $asdf% the result is: asdf{TAB}$asdf (ding)
Only the % symbol seems to be a problem. I'm running 8.0.10 on Win 8 Release Preview (I'll be changing to Win 8 RTM in the next few days).
BTW - working on a holiday? That's dedication! :)
I tried the same macro on a Win 7 Ultimate 64 bit laptop with v8.0.11 with same results for the % symbol.
But now there is another strange issue only on Win 7: special keys in macros like {TAB} and {ENTER} behave strangely and don't type out. With username asdf and password &asdf the macro $USERNAME${TAB}$PASSWORD${ENTER} results in asdf&asdf. When it gets to the {TAB} part it appears to type in ALT+TAB because the Task(Window) Switcher pops up (and stays on the screen). Also the ENTER key doesn't appear to be typed out. Lastly if I repeatedly try this macro, sometimes the macro is cut short like these: asdf&as, asdf&a, asdf&.
** OK I tried setting an Initial Wait time of 2 sec for the macro and this fixes all the issues except the % symbol one. With initial wait of 1 sec there are still the odd times where there are some issues. It appears to me that with wait time of 0 sec the macro starts so fast that it registers that I'm still holding down one or more of the CTRL+ALT+A keys and modifying the typed character (even though i have physically stopped pressing the keys before the macro even starts typing). Strangely this doesn't occur on the Win 8 desktop. Win 7 laptop uses Intel Core i5-560M with 8GB RAM; desktop uses Intel Core i7-3770K w/ 16GB RAM.
Could you export me data entry, anyone that does not work?
David Hervieux
Here's the export file.
Also, I use SQL Server data source with shared passphrase security provider to fully encrypt the database. In case that causes any issues when storing/retrieving the macro keys.
edited by _RNK_ on 1/2/2013
Could you export it as a session and not an xml? With the Xml I don't have the macro included.
edited by dhervieux on 1/2/2013
David Hervieux
Here's the session file with credential.
edited by _RNK_ on 1/2/2013
test.rdm
This is still on my todo list. I just want to let you know that I haven't forgotten you.
David Hervieux
Thanks David! Just to update this, I've since installed a fresh copy of Win 8 Pro 64 bit RTM (I was on Release Preview before) and the first app I installed is RDM to try this again, and the problem is still there.
No rush on this as currently it only affects some routers and switches I manage.