Saved sign-in for SSO and MFA apps: sign in once, run headless
Tags: sso, single sign-on, mfa, saved sign-in, auth state, entra id, okta, headless, ci, session, persistent profile, attach browser, oauth2
Most business apps sit behind single sign-on (Microsoft Entra ID, Okta, Google and others) with MFA. That is usually where test automation stops. WebSureQTool 1.5 separates the one human sign-in from every later run. HOW IT WORKS 1. A person signs in once, in a real browser, completing MFA as usual. 2. WebSureQTool saves the cookies of every domain the sign-in touched, plus local and session storage, encrypted for your Windows user. 3. Suites that use the saved sign-in load it, prove it still works by checking an element that only exists when signed in, and refresh it after each passing run. 4. When the identity provider ends the session, the run stops immediately and names the exact command to sign in again. It never hangs waiting for a person. SAVE A SIGN-IN - In the app: Tools > Start Manual Login Session..., sign in, and confirm. Manage saved sign-ins under Tools > Saved Sign-in States (SSO)... - From the command line: wsq auth login <sign-in URL> --key <name> --post-login-check "<selector that only exists when signed in>" USE IT IN A SUITE Set the suite's session to use the saved sign-in and give it the same signed-in check. From the command line, add --auth-state <name> to wsq web-run. WHEN THE IDENTITY PROVIDER IS STRICT - Persistent browser profile: keeps "stay signed in" cookies, passkeys and device-bound policies between runs. - Attach to your own browser: start Edge or Chrome with remote debugging, sign in there (Windows Hello and smart cards work), and let WebSureQTool drive that browser. - API sign-in: the OAuth 2.0 token step gets a token (client credentials, refresh token, password or authorization code) and authorizes the HTTP steps that follow. WHAT IT DOES NOT DO Saved sign-in never bypasses MFA, CAPTCHA or bot detection, and it never stores your password. It reuses what the identity provider issued to you, and the saved file only decrypts for the Windows user who saved it.
Need the detailed workflow?
The public guide stays intentionally high level. Open the Intelligent Assistant for click-by-click instructions, learning order, and practice ideas.
Open Assistant
