Active Sessions Management

Sessions page provides full management for real-time active user connections, connected device details, and session termination controls.

What are Sessions?

Sessions represent active authenticated connections between client applications and the AuthVaultix server.

The session lifecycle operates in three primary stages:

Session Initialization: On client app startup an init API call is made and a unique session string is generated.

Session Validation: When the user logs in or completes license activation the session is marked Validated and bound to the user account and HWID.

Session Termination: A session ends when the app calls logout on exit, when an expiration timer elapses, or when the session is terminated via the dashboard or seller API.

Session Identification Parameters

The dashboard session list displays the following details for each active connection:

Parameter Field	Description	Example
Session ID	Unique cryptographic connection string.	`sess_8947291048291048`
User Credential	User account name ya bound license key.	`luffy_dev`
IP Address	Connected client IP address.	`152.58.135.231`
Hardware ID (HWID)	Bound machine hardware signature hash.	`58C1-C9C4-385B-62E3`
Last Active Time	Last API request validation timestamp.	`2 Minutes ago`

Single Session vs Emergency Kill All

The dashboard provides two session termination options:

Kill Single Session (kill_one):

Inspect a specific user connection and click the red Kill button on that row.

After confirming the action the specific session_id is removed from the database and the client's next request is immediately blocked.

Kill All Sessions (kill_all - Emergency Kill Switch):

Click the Kill All button in the top header to terminate all active users for the selected application at once.

Confirmation Alert: "Are you sure you want to kill ALL sessions? This will logout everyone."

Use this during security incidents or major deployments to force an immediate logout for all users.

Unique Sessions & Auto-Logout Best Practices

Unique Session Constraint: Only one application session per machine is allowed. If a user restarts the application without gracefully logging out, the new session will automatically overwrite the old session to prevent session spamming.

Developer Best Practice (logout): Developers should call the logout API on application close events so server resources are released gracefully.

Search & UI Controls

Active Sessions Counter Badge: The top header counter badge displays the live active connection count (count($sessions)).

Live Search Filtering (#searchBox): Use the search input to filter list items by Username, IP Address, HWID, or Session ID.

Mobile Responsive Layout: The UI adapts to mobile with compact session cards for smaller screens.

Sessions

Active Sessions Management#

Sessions page provides full management for real-time active user connections, connected device details, and session termination controls.#

What are Sessions?#

Session Identification Parameters#

Single Session vs Emergency Kill All#

Unique Sessions & Auto-Logout Best Practices#