---
title: "Two Step Authentication"
slug: "two-step-authentication"
updated: 2023-01-06T15:48:57Z
published: 2023-01-06T15:48:57Z
canonical: "docs.catchpoint.com/two-step-authentication"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.catchpoint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Two Step Authentication

Catchpoint tests do **not** support two step authentication due to the stateless nature of the Catchpoint agents.

The Catchpoint agent waits the specified time denoted by the second parameter, but does not reflect it in the <a href="https://docs.catchpoint.com/docs/Response-vs-Document-Complete-vs-Webpage-Response" target="_blank" rel="noopener">Webpage Response</a> metric. This is by design, as reporting it would cause the agent to automatically add 30 seconds for every failure of the <a href="https://docs.catchpoint.com/docs/transaction-commands-and-macros#waitForElcodeentPresent" target="_blank" rel="noopener">waitForElementPresent</a> verb.  This would not be reflective of the actual performance of the site. The agent "realizes" it waited 30 seconds for the element to load, but noticed that nothing occurred on the wire. Instead of adding the 30 seconds in which nothing happened as the result of your site to Webpage Response, the agent reports the time of the last relevant event, which for this waterfall was finishing downloading content on the wire. If the agent found the element, *then* it would have added it to Webpage Response, as it would have been relevant as you are searching for it specifically within the script.