Token Management
Ingest tokens authenticate your edge devices with FleetManager. Each token is bound to a specific customer.
Creating Tokens
- Open Customer Management and select the customer
- Click Create Token
- Optional: Set an expiration date
- The token is displayed — copy it immediately, it is shown only once
Token Properties
| Property | Description |
|---|---|
| Prefix | First 8 characters for identification |
| Customer binding | Token is valid only for the assigned customer |
| Expiration date | Optional, token becomes invalid after this date |
| Last used | Timestamp of last successful authentication |
Using Tokens
Devices send the token as a bearer token in the HTTP header:
Authorization: Bearer fm_abc12345...The token authorizes sending heartbeats, diagnostics, and status for the assigned customer.
Revoking Tokens
- Open the token list for the customer
- Click Revoke next to the token
- The token is immediately invalidated
Revoked tokens cannot be reactivated. Create a new token if needed.
Expiring Tokens
Under Settings, a global auto-rotation policy can be configured. Tokens that are about to expire can be queried in advance.
Best Practices
- One token per device or device group — makes targeted revocation easier
- Set expiration dates — especially in regulated environments
- Rotate regularly — renew tokens before they expire
- Never commit to source code — store tokens in config files or environment variables