Explain how eValid handles cookies and session cookies

Discussion of the technology underlying the eValid solution.

Explain how eValid handles cookies and session cookies

Postby MLinda » Thu Nov 11, 2021 10:14 am

Hello.

Please explain about how eValid Handles Cookies and Session Cookies?

Thanks in advance.
MLinda
 
Posts: 1
Joined: Thu Nov 11, 2021 10:02 am

Re: Explain how eValid handles cookies and session cookies

Postby eValid » Fri Nov 12, 2021 9:39 am

MLinda wrote:Hello.

Please explain about how eValid Handles Cookies and Session Cookies?

Thanks in advance.


Thanks for asking MLinda.

* Basic Ideas

When navigating to or entering a secure session in a website, you are often prompted by a message -- usually a Modal Dialog -- which informs the user of the current state of the browser.

For example, it might tell you that you don't need to log on because you already are logged on.

It knows this because the server has left a session cookie (which stays in memory for some length of time) or a cookie file stored in the browser cache area.

If you've deleted the server's cookie from your cache, or if you've turned off your browser and restarted it before playback, the server will behave differently.

The bad news is that your test script might fail.

To test this type of websites, you have to be aware that there will be different server responses depending on how the script is launched and the state of the browser.

* Assuring Consistent Playback: Session Cookie Used

Playing back an eValid test script which visits a login site that uses a session cookie requires some care.

By launching it normally (for example, by using "eValid: Open eValid > Load Script > Playback Script") causes eValid to pause for manual intervention upon displaying of a Modal Dialog indicating either the current status or a user log in prompt.


Running the same script multiple times without closing eValid may cause the website to maintain a state where subsequent runs are not presented with the same security window after the initial login.

For scripts that require constant opening and closing of the eValid browser such as running a script in batch mode, we recommend the use of the ModalDialog Commands of eValid to simulate the interaction on a security alert on screen.

Because the session is constantly terminated due to the closing and opening of eValid, the user can also use the -S switch to suppress modal dialogs which may appear unexpectedly during script playback.

However, scripts that are run multiple times without eValid being closed only produces the security window once, during the beginning of playback and does not return unless the eValid session is terminated or closed.

* Changing eValid Settings

To change your existing cookie settings, click on "eValid > Settings > Cache Manager" or Press F2.

Command line switches on cookie management can be found in the eValid User Manual ("eValid: Help > Documentation > User Manual > Technical > Command Line").


-- eValid Support
eValid
 
Posts: 2392
Joined: Tue Jan 01, 2008 12:48 pm
Location: USA


Return to Technology

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