Skip to content
OriginChats

auth

auth is implemented by handleAuth in src/api/handlers/auth.osl.

Validates the connection-specific Rotur validator, records the login, establishes presence, and emits the ready sequence.

Access

Section titled “Access”
Gate Requirement
Authentication Not required; this command establishes authentication.
Central permission None. Resource, channel, ownership, or hierarchy checks may still apply in the handler/helpers.
Broadcast Not marked global directly by this adapter. A helper may emit focused or server-wide updates.

Request

Section titled “Request”

Every request includes cmd: "auth" and may include an opaque listener correlation value.

Field Validation / meaning
validator Read separately by the handler or a shared domain helper

Validator source

Section titled “Validator source”

This adapter delegates validation to a shared helper. The field table lists values read directly by the handler; follow the collaborators below for the shared domain schema.

Processing path

Section titled “Processing path”
  1. handleCmd enforces authentication.
  2. dispatchCmd routes auth to handleAuth.
  3. The adapter validates and normalizes input, then calls its domain collaborators.
  4. Durable mutations complete before the response or event is returned.
  5. onMessage adds the request listener to direct responses and performs any marked broadcast.

Direct collaborators visible in the handler: encodeURIComponent, get, success, catch, userFromId, userLoginRecord, userStatus, isNewUser, broadcastAuthed, userToPublic

Responses and events

Section titled “Responses and events”

Response/event command names visible in this adapter: auth_error, user_join, user_connect, auth_success, ready.

Validation and domain failures use:

{
  "cmd": "error",
  "val": "<message>",
  "src": "auth",
  "listener": "<copied from request>"
}