> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://tester.army/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://tester.army/_mcp/server.

# Auth Troubleshooting

Use this page when a test cannot authenticate into the app under test.

## Missing login credentials

If a test has a login step but no saved credential is available, add one under **Project → Test Accounts**.

See [Test Credentials](/auth/credentials).

## Saved credential rejected

If the app rejects a saved username or password:

1. Confirm the credential works in a normal browser.
2. Update the saved credential in TesterArmy.
3. Check whether the account is locked, expired, or requires password reset.
4. Retry the run.

## Email and OTP login

For magic links, OTP codes, invitations, or password resets sent by email, use an Agent Mail inbox.

See [Agent Mail Inboxes](/auth/agent-mail-inboxes).

## Phone and SMS OTP login

For flows that verify a phone number or send login codes by SMS, the agent can use a real test phone number and read the verification code from the incoming message.

See [SMS Phone Numbers](/auth/sms-phone-numbers).

## Unsupported auth blockers

Some auth flows need product or environment changes before an agent can complete them reliably:

* CAPTCHA or bot challenges
* Required MFA with an authenticator app (email and SMS paths are supported)
* Device approval prompts
* SSO policies that block automated browsers

Create a dedicated QA account or staging auth path for automated testing.

## HTTP Basic Auth

If the browser shows an HTTP Basic Auth prompt before your app loads, configure site protection credentials instead of app login credentials.

See [HTTP Basic Auth](/auth/basic-auth).