Real‑time subscription token expiration ambiguity in SurrealDB 1.0.0

Goal

To validate real‑time subscription behavior in a sandboxed SurrealDB 1.0.0 environment without exposing production credentials.

Constraints

Use Docker or the SurrealDB Playground to spin up a local instance, establish a WebSocket subscription, and monitor session token validity over time.

Uncertainty

The documentation does not define whether session tokens expire after inactivity, after a fixed duration, or only on server restart. This ambiguity could affect long‑running subscription integrations.

Questions

1. What is the exact expiration policy for session tokens issued during authentication in SurrealDB 1.0.0?
2. Does the token lifetime differ between community and enterprise editions?
3. Can token validity be configured (e.g., timeout settings) or is it fixed by the server?