Tokens Management#
The AuthVaultix Developer Dashboard Tokens Management page gives you complete control over generating application pre-authentication tokens, monitoring their status, configuring token validation, and revoking compromised tokens.
What are Tokens?#
Tokens act as a secondary pre-authentication verification layer in the AuthVaultix platform.When you enable the Token Validation feature in Application Settings, client software must provide a valid token before starting the authentication process.AuthVaultix tokens begin with a standard prefix:
avx_ followed by cryptographically secure random hex bytes (Example: avx_7f8a9b0c1d2e3f4a5b6c7d8e9f0a1b2c).The token format is automatically generated by AuthVaultix. Developers should not manually create or modify tokens.
How Tokens are Created#
AuthVaultix tokens are generated and assigned in two ways:1.
Application-Level Token Generation: When the developer turns ON the Token Validation toggle in App Settings, a primary verification token is generated for the application.
2.
User & License Provisioning: When a new user or license is created from the dashboard, there may be an option to generate and link a token automatically if enabled.
Key Differences: Tokens vs Licenses#
| Feature Comparison | Tokens | Licenses |
|---|
| Usage Stage | Pre-Authentication Stage: Checked during session initialization before software starts. | Authentication Stage: Used during user login or registration. |
| Primary Purpose | Block unauthorized client startup and control application execution. | Unlock user subscription access and register accounts. |
| Prefix Format | avx_ prefix with secure random bytes. | Custom masks (Example: ****-****-****-****). |
| Client Requirement | Checked before the client login screen renders. | Entered in the user login or sign-up form. |
The effect on existing authenticated sessions depends on application configuration and session validation policy.
Where does the client store and pass the Token?#
Where the token is stored depends entirely on the developer’s client-side implementation:Local Storage Locations: The client can save the token as an encrypted file in the App Root Directory, %APPDATA%, %TEMP%, or the Windows Registry.
API Pass Parameter: In the session initialization request, the client passes the token or tokenpath parameter. AuthVaultix verifies the token signature and grants a valid session.
Token Revocation & Status Controls#
On the dashboard page (page=tokens), you can inspect and manage active token status:1.
Token Validation Status Indicator:Active: Token validation is ON and active tokens are displayed in the filtered view.
Disabled Alert: If Token Validation is OFF in App Settings, a warning message is shown.
2.
Revoking Tokens (action=revoke):If a token is compromised or authorization must be canceled, the developer can execute Revoke Token from the dashboard.
A revoked token immediately blocks all future initialization requests.
3.
Once a user or license token is generated, the existing token cannot be modified or overwritten. To issue a new authorization, revoke the old token and issue a new one.
Modified at 2026-07-26 18:40:40
