Feature Request: Optional per-device / per-session authentication token for location reporting

Optional per-device / per-session authentication token for location reporting

Currently, the device identifier is effectively enough for a client to submit positions to a device.

For permanent deployments this may be acceptable, but for temporary or recurring deployments it can create problems.

Problem

We use Traccar for recurring cycling events.

Participants receive temporary device identifiers such as:

001 002 003

These identifiers may be reused in future editions of the event.

For example:

• Event Summer Race, 2026 uses device ID 001
• Event Winter Race 2026 also uses device ID 001
• ....

If a participant from the previous event still has Traccar Client configured and active, that old device could potentially continue submitting positions using the same identifier.

This can result in stale or incorrect positions appearing during a new event.

Proposed solution

Add support for an optional authentication token associated with the reporting device or reporting session.

Example:

deviceId=001
token=6f8c2f0d...