DEV Community

SorrelThorncroft
SorrelThorncroft

Posted on

Exceptionless Scopes Show Why a Project Token Is Not a User Token

Exceptionless Scopes Show Why a Project Token Is Not a User Token

Exceptionless collects errors, logs, and events for applications. It supports hosted and self-hosted deployments and uses bearer tokens for API access. The scope of those tokens determines whether a caller can submit project data or administer the whole account. That distinction is central to a safe deployment.

A count-only query for title="Exceptionless" returned 727 matches at 05:44:56 CST on 20 November 2026 with sub_type=all, page 1, and pagesize 1. The result is a title match count, not a confirmed list of running services. It can include project pages and unrelated uses of the word.

User scope is the keys to the kingdom

The Exceptionless API documentation describes a user scope with full administrative access and a client scope for posting and reading events and configuration for a project. It explicitly warns that user-scoped tokens should be protected. A user token can create projects and change account settings; a project token should not be treated as a replacement for an administrator session.

Inventory both token types. Assign each one to an application, owner, and purpose. Revoke unused tokens and set a review date. The submission token used by an application should not be stored in the same secret store as the administrator token. If the application is compromised, the blast radius should stop at its project.

Error events are not automatically safe

Exceptionless project settings include data exclusions and client configuration. The documentation notes that reports can contain sensitive fields and that exclusions can remove named fields from error data. Use exclusions for known secrets, but also review the application's own logging. A password in a stack trace or a cookie in request metadata is a data-handling problem before it reaches the tracker.

Restrict who can search and export events. Protect organization and project membership. Review webhook and notification destinations, since they may receive error context or links to it. Keep a retention period that matches the incident response and privacy requirements.

Verify the deployment boundary

For self-hosted deployments, confirm the web and API endpoints, TLS, identity provider, and database. The first account created in a simple local run is an administrator, which is convenient for evaluation and unacceptable as an unplanned production control. Create named users, remove test accounts, and require strong authentication.

For hosted use, review the organization's project roles and API key handling. A public title match does not tell you which hosting model is in use. Do not attempt to log in to unknown instances. Use DNS, certificate transparency, and your own cloud inventory to identify owned assets.

A testable review

Create a project-scoped client token and confirm that it can post an event but cannot create a project or change billing or organization settings. Revoke it and verify that new submissions fail. Test a user token with the expected administrator role, then test a lower-privileged user. Check that excluded fields are absent from a test event.

The 727 title matches should be reconciled with owned hosts before any response. Exceptionless is valuable because it turns application failures into evidence. The access model must preserve that evidence while keeping a project key from becoming an account-wide capability.

References

Top comments (0)