DEV Community

jeffrey
jeffrey

Posted on

Yamtrack registration and OIDC scopes define the exposed account path

Yamtrack registration and OIDC scopes define the exposed account path

Yamtrack is a self-hosted media tracker built on a Django application. A public instance can expose account registration, social login, OpenID Connect, personal watch history, and application administration. The product is small in the current measurement, which makes owner validation more practical.

On 2026-11-17, title="Yamtrack" returned 101 total matches at 07:47:02 +08:00. http.body="Yamtrack" returned 135 at 07:47:03 +08:00. Both used sub_type=all, page 1, and pagesize=1. The close values reduce the false-positive gap, but the count still describes pages rather than authenticated user populations.

Registration is a product setting

The official environment-variable documentation lists a registration toggle and says it defaults to enabled. That makes the state of a new deployment an owner decision. A private instance should disable open signup before it is announced or indexed, unless the business model intentionally provides self-service accounts.

Social authentication adds another account-creation path. The Yamtrack social-authentication guide shows OpenID Connect configuration with an example GitHub scope that includes repository permissions. A deployment should request only the claims and scopes it needs. A tracker does not need repository access to identify a user.

Host and CSRF settings matter behind a proxy

The environment variables include ALLOWED_HOSTS and a CSRF-trusted-origin setting for deployments behind a reverse proxy. A host allowlist that is too broad can make virtual-host validation less useful. A CSRF origin that is too narrow breaks login and profile changes. Both should match the public URL and proxy trust model.

Review the OIDC client secret storage, logout behavior, provider outage path, and recovery for a user whose provider identity changes. The tracker data is personal, so account deletion and export should be deliberate. Public demo accounts need a separate lifecycle from production users.

Use the count as a small validation set

With 101 title matches, an owner can inspect a substantial portion directly. Check the registration page, provider redirect, public URL, certificate, and instance owner. For the 135 body matches, distinguish product pages from documentation and unrelated text.

The useful inventory fields are registration state, OIDC provider, social scopes, admin users, database location, and backup owner. The title value in this sample is a starting point, not a claim that every match is a live public Yamtrack service.

References

[1] ZoomEye title query. https://www.zoomeye.ai/searchResult?q=dGl0bGU9IllhbXRyYWNrIg%3D%3D

[2] ZoomEye body query. https://www.zoomeye.ai/searchResult?q=aHR0cC5ib2R5PSJZYW10cmFjayI%3D

[3] Yamtrack environment variables. https://fuzzygrim.github.io/Yamtrack/dev/env-variables/

[4] Yamtrack social authentication. https://github.com/FuzzyGrim/Yamtrack/wiki/Social-Authentication-in-Yamtrack

Top comments (0)