Menu

Matomo token_auth placement decides where secrets leak
📰

Matomo token_auth placement decides where secrets leak

DEV Community: authentication·jeffrey·10 days ago
#KH0h52TQ
#devtoauthentication#devto#dev#token#matomo
Reading 0:00
15s threshold

Matomo token_auth placement decides where secrets leak

Matomo uses token_auth for Reporting API calls, authenticated Tracking API requests and embedded widgets. The token is not just an analytics-read key. Matomo's documentation compares it to a user's password and explains that a token can be sent in a GET query string or a POST body. The HTTP method therefore changes where the secret can appear in logs, browser history, proxies and support bundles.

On 2026-11-05, a count-only ZoomEye query with sub_type=all , page 1 and page size 1 returned 30,589 matches for app="Matomo" . The title query returned 34,688. These counts locate application surfaces, not installations with weak tokens or exposed reports.

Matomo 6 documentation adds a token access level and an "Only allow secure requests" option. A secure token is accepted only in POST requests, not as a URL parameter. The option is useful only when the integration can actually use POST.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.