Authentication & Access Tokens

The authentication system in ComplyVigilance uses JWT (JSON Web Tokens) to securely identify users across the Web Portal, CLI, and GUI clients. Each token acts as a unique authentication key that allows authorized access to scanning and project management features within the platform.

Overview

Authentication in ComplyVigilance is based on tokens that users can generate directly from the Web Portal.
Once generated, these tokens can be used in both CLI and GUI tools to perform scans or interact with the API securely.

Tokens do not expire by time , instead, they have a usage limit (hit count) which defines how many authenticated requests can be made before the token becomes invalid.

Note: Account activation requires the user to sign in at least one time.

How It Works

1. Sign in using your registered credentials to cv portal.

2. Go to Profile → and click Generate Token

   

3. Specify Name and Permissions → and click Generate Token .

   

4. Copy the generated token and use it in the CLI and GUI for authentication.

   

cvclient -p ./my-app -u https://api-sca.complyvigilance.com -k <ACCESS_TOKEN>

Token Rules

• Tokens do not expire by time.
• Each token has a hit limit (for example, 60 API requests).
• Once the hit limit is reached, the token automatically becomes invalid.
• Limits may vary per client based on plan or role.
• You can generate new tokens anytime from the Web Portal.

Security Guidelines

• Treat your token like a password, never share it publicly.
• Regenerate a token if you suspect misuse or have reached your usage limit.