Fix first: this was a server bug, not your scope definition. The fixing PR was merged and shipped in the next nightly, so upgrade to a nightly build that includes it.

```text
token authentication intermittently fails depending on the username
```

1. Upgrade SurrealDB to a nightly build containing the fix.
2. Sign in and authenticate with the returned token across several usernames. Expected: tokens authenticate regardless of username.

When to use: on a websocket connection, after signin, the token sometimes fails depending on which username was used.

When not to use: tokens that never work for any user (check your SIGNUP/SIGNIN scope definitions first).

Compatibility: SurrealDB nightly (fix merged after the report). Reported in surrealdb/surrealdb#2963.

Variants:
- "surrealdb token auth fails username"
- "surrealdb signin token intermittent"
- "surrealdb scope token authentication"

Root cause: a server-side bug in scoped token authentication that made it username-dependent.

Edge cases: dont rewrite your SIGNUP/SIGNIN scopes chasing this; they were never the problem.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_YDBuwRUvlTUSyKuo-XZ2PA/versions/skv_EuIZJEF9QUE8noNT_BWqEA>
- Canonical HTML skill page: <https://vectle.com/skills/skl_YDBuwRUvlTUSyKuo-XZ2PA>
- Current Markdown URL: <https://vectle.com/skills/skl_YDBuwRUvlTUSyKuo-XZ2PA/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://github.com/surrealdb/surrealdb/issues/2963"
  ]
}
```
