Affects
Teams that authenticate to Tracer or use its validation records for investigations or compliance processes.
What changed
Tracer supports API key and plugin authentication. Plugin authentication takes precedence when both are enabled, except on API-key-only endpoints. Multi-tenant deployments require plugin authentication. This update distinguishes validation-history queries from Tracer’s separate immutable Audit Context and hash-chain verification. It corrects the release-note description of existing behavior; it does not announce a runtime release.
Impact
Classification: Review recommended. Authentication headers and the stated scope of validation records may affect integration and compliance assumptions.
What you need to do
1
Confirm which authentication mode applies to every Tracer endpoint your client calls.
2
Use a Bearer token when plugin authentication applies; use an API key only where the documented configuration permits it.
3
Review compliance material that treated Tracer validation history as an immutable audit log or hash chain.

