Skip to main content
Avoid using Momentic tests to log in using SSO. Providers like Google, Facebook, and GitHub often have security measures that block automated browsers.
This page covers how to obtain credentials for specific login mechanisms. For where to put login steps (inline, in the before section, or a cached auth module) and which approach to choose, see Authentication strategies.

​
Username and password

The simplest case: add a Type step for the username, a Type step for the password, and a Click on the submit button. Pull the values from environment variables ({{ env.TEST_USERNAME }}) rather than hard-coding credentials in the test file.
Prerequisites: An email address must be provisioned by Momentic.
Add a JavaScript step with the following content:
Use the Save to environment variable option to save the link to an environment variable, e.g., MAGIC_LINK. Then, use the Navigate step with content {{ env.MAGIC_LINK }} to navigate to the magic link and complete the login process.

​
Email One-Time Password (OTP)

Prerequisites: An email address must be provisioned by Momentic.
Add a JavaScript step with the following content:
Use the Save to environment variable option to save the code to an environment variable, e.g., OTP_CODE. Then, use the Type step with content {{ env.OTP_CODE }} to input the OTP code and complete the login process.

​
SMS One-Time Password (OTP)

Prerequisites: A SMS number must be provisioned by Momentic.
Add a JavaScript step with the following content:
Use the Save to environment variable option to save the code to an environment variable, e.g., OTP_CODE. Then, use the Type step with content {{ env.OTP_CODE }} to input the OTP code and complete the login process.

​
Vercel Deployment Protection

Follow Vercel’s protection bypass for automation guide. Configure the bypass header in your test options.

​
IP whitelist

For teams that use the Momentic dashboard, whitelist Momentic’s fixed egress IP: 34.106.239.183. For Azure-hosted customers, whitelist 52.177.232.247.