Input Strings

Discussion of the technology underlying the eValid solution.

Input Strings

Postby Sam08 » Mon Sep 01, 2008 5:50 pm

What about different types of Input Strings?
Sam08
 
Posts: 32
Joined: Sun Jul 06, 2008 10:01 am

Re: Input Strings

Postby technology » Mon Sep 01, 2008 5:52 pm

Thanks for posting

(1) Regular HTML (in browser) input text commands obey the
option the record the typed-in information in encoded form, and these
commands automatically emit the un-encoded (i.e. decoded) text as needed
during playback.

(2) The same applies when you are using Application Mode and/or Desktop Mode
(F12 or Ctrl-F12). The input fields are encoded at record time and
invisibly decoded at playback time.

(3) The AuthenticateUser command handles the situation when a
user authentication popup appears, and in this case the account name
and the password are both recorded in plain text (unencoded) in the
script. However, the GUI display at playback time continues to
show the "o o o ..." on the user authentication popup...

(4) That the script has the password in plaintext is an advantage:
way you can modifiy the account/password manually without having to
re-record the script.

(5) We don't know for sure, because the working of the user authentication
is some deep in the browser, if we can modify that feature to encode
the password section. Obviosly we dont' want to record "o o o ..."
in the script (i.e. what appears in the box when you type in actual
letters) because that won't authenticate...

We can consider this but because we have had no complaints or
objections this is not something we would dive into automatically...
I mean, as part of our internally funded development effort...

(6) I think at this point you need to be considering having the
monitoring machines themselves somehow under lock and key...
eValid Tech Support Team
technology
 
Posts: 53
Joined: Tue Jan 01, 2008 12:48 pm


Return to Technology

Design Downloaded from free phpBB templates | free website templates | Free Web Buttons