Eversheet Web CDP Auto Login Flow

Problem Being Solved

Eversheet Web automation tasks often stall at the login stage: the page may not be a standard login form but an intermediate login page, or it may require clicking a “System Account Login” entry before username and password fields appear. A simple “open page, enter credentials, click login” approach can easily stop on the wrong view. In addition, login URLs, usernames, and passwords should not be hardcoded in skills or scripts, especially across environments, tenants, or unattended runs.

How It Works

The skill abstracts login into a set of verifiable Chrome CDP steps, with the core principle of executing the flow without storing credentials. baseUrl, username, and password must be supplied by the current task, runtime parameters, environment variables, or secure configuration. If any required value is missing, the flow should report the missing input instead of guessing or filling a default.

A typical execution path is:
- Open baseUrl and determine whether the current page is already a login page or an intermediate login view.
- If the page contains a “System Account Login” entry, click it first to enter account/password mode.
- Locate the username field, password field, and login button, then fill and submit the externally provided credentials.
- Wait for post-login navigation, home page loading, or stable page state.
- Confirm whether the system has actually been entered, rather than remaining on a login or error page.

The success criteria are concrete: the login form disappears, the current page reaches the system home or target home, the page is in a logged-in state, and no obvious login error is shown. The skill does not treat “the login button was clicked” or “a token was generated” as completion, because intermediate states can still fail.

Scope and Caveats

This skill is useful as a prerequisite for Eversheet system login, unattended entry to the home page, and follow-up page validation. It depends on Chrome CDP runtime capabilities but does not choose the browser medium or own the Chrome launch strategy. The runtime environment must already provide a usable CDP session or browser control capability.

Three points matter: first, all inputs must be externally supplied, avoiding hardcoded addresses, accounts, or passwords; second, if the page structure changes and the login entry cannot be identified, the flow should remain diagnosable instead of submitting blindly; third, downstream business validation should continue only after a logged-in context is confirmed, not after the login button click alone.