GameServer.Accounts.UserToken (GameServer v1.0.509)

Functions and schema for persistent user tokens used by sessions, magic links, and email-change workflows.

Tokens generated by this module are stored hashed when sent via email and stored raw for session tokens (which are signed). The module provides helper queries for verification and convenient builders used throughout the app.

Summary

Types

t()

Functions

build_email_token(user, context)

Builds a token and its hash to be delivered to the user's email.

build_session_token(user)

Generates a token that will be stored in a signed place, such as session or cookie. As they are signed, those tokens do not need to be hashed.

verify_change_email_token_query(token, context)

Checks if the token is valid and returns its underlying lookup query.

verify_magic_link_token_query(token)

Checks if the token is valid and returns its underlying lookup query.

verify_session_token_query(token)

Checks if the token is valid and returns its underlying lookup query.

Types

t()

@type t() :: %GameServer.Accounts.UserToken{
  __meta__: term(),
  authenticated_at: DateTime.t() | nil,
  context: String.t() | nil,
  id: integer() | nil,
  inserted_at: DateTime.t() | nil,
  sent_to: String.t() | nil,
  token: binary() | nil,
  user: GameServer.Accounts.User.t() | Ecto.Association.NotLoaded.t() | nil,
  user_id: integer() | nil
}

Functions

build_email_token(user, context)

Builds a token and its hash to be delivered to the user's email.

The non-hashed token is sent to the user email while the hashed part is stored in the database. The original token cannot be reconstructed, which means anyone with read-only access to the database cannot directly use the token in the application to gain access. Furthermore, if the user changes their email in the system, the tokens sent to the previous email are no longer valid.

Users can easily adapt the existing code to provide other types of delivery methods, for example, by phone numbers.

build_session_token(user)

Generates a token that will be stored in a signed place, such as session or cookie. As they are signed, those tokens do not need to be hashed.

The reason why we store session tokens in the database, even though Phoenix already provides a session cookie, is because Phoenix' default session cookies are not persisted, they are simply signed and potentially encrypted. This means they are valid indefinitely, unless you change the signing/encryption salt.

Therefore, storing them allows individual user sessions to be expired. The token system can also be extended to store additional data, such as the device used for logging in. You could then use this information to display all valid sessions and devices in the UI and allow users to explicitly expire any session they deem invalid.

verify_change_email_token_query(token, context)

Checks if the token is valid and returns its underlying lookup query.

The query returns the user_token found by the token, if any.

This is used to validate requests to change the user email. The given token is valid if it matches its hashed counterpart in the database and if it has not expired (after @change_email_validity_in_days). The context must always start with "change:".

verify_session_token_query(token)

Checks if the token is valid and returns its underlying lookup query.

The query returns the user found by the token, if any, along with the token's creation time.

The token is valid if it matches the value in the database and it has not expired (after @session_validity_in_days).