For teams whose runs stop at the sign-in page.

Your setup

Sign-in shows a captcha or a bot check, goes through SSO (Google, Okta, Microsoft Entra), or asks for a code.
Runs stop at sign-in, or test cases end as blocked.
You want runs to sign in on their own, also at night.

Say this to Certyn

Your runs can't log in to staging. There is a reCAPTCHA on the login page and our accounts use Okta SSO. How do we fix this?

Opens the sign-in on a Machine to see what stops it.
Picks the way for each case:
- Captcha or bot check: Certyn does not solve them. Turn the check off on staging, use your captcha provider's test keys there, or allow the runner's IP (see Certyn Cannot Reach Your App).
- SSO: a test account that signs in with a password. Certyn opens the sign-in form and saves LOGIN_USERNAME and LOGIN_PASSWORD.
- Authenticator 2FA: a secret form for TOTP_SECRET (the setup key). Runs make the codes.
- Email code at sign-up: nothing to set. Runs have an inbox of their own and read the code.
- Email or SMS code on an existing account: a test account without it.
To check something now, in the chat: when a step needs you (a captcha, an SSO page, a code), Certyn writes the exact step and waits. You do it on the Machine in the live view, then Certyn goes on.
Offers to restart the Machine for new variables, and a short run that signs in. It asks first.

You type passwords and keys only in the forms. The chat never sees them.

Runs that sign in on their own, also on a schedule and after each deploy, and test cases that reach the pages behind sign-in.

Runs cannot pass a captcha or a bot challenge, and cannot wait for you. A handoff works only in the chat, on its Machine.
A sign-in you do yourself stays in that Machine. Runs do not reuse it.
SMS codes do not work. A run waits at most 3 minutes for an email.
The run inbox belongs to runs. The chat cannot show its address.
With no password test account for an SSO app, runs test only the pages that need no sign-in.