Files
chess-endgame-trainer/lib/chesstrainer/accounts/role.ex
T
owenrees 624ddab644 Admin panel, login throttling, and Cloudflare edge hardening (#150)
* Document the remote shell for production user management

* add sitemap to footer links

* remove border under theme selection

* Add admin theme and user management (#144)

Add /admin/themes CRUD and /admin/users list/detail with role and plan editing, guarded by a shared Policy module. Include last-super-admin and self-role protections plus structured id-only admin logs.

Also add admin invitations, confirmation resends and password-reset emails, which work in development through the Swoosh mailbox before SES is configured.

* Rate-limit password logins and emit auth events (#142)

Add a two-bucket login throttle (5 failures per login, 10 per IP in a 15-minute window) and a shared client-address helper for controllers and LiveViews. Blocked attempts skip the database and bcrypt.

Log auth.login.failed and auth.login.throttled warnings with boot-scoped HMAC addresses only, and stop repeated confirmation emails on unconfirmed login attempts.

* Harden the production login edge for Cloudflare

Document the layered login defence: the app throttle is primary, Caddy must pass Cloudflare's CF-Connecting-IP to the app, and Cloudflare edge rate limiting covers request floods.

Update the reference Caddyfile to accept only Cloudflare ranges and reject direct-to-origin traffic, and document the exact Cloudflare dashboard rules.

* Document 10-second Cloudflare rate-limit window

Cloudflare may only offer a 10-second period. Keep the edge rule at 10 login POSTs per 10 seconds per IP and rely on the app's 15-minute login/address throttle for credential guessing.

* Document Cloudflare limits for LiveView registration

Registration submits over the shared LiveView socket, so a Cloudflare rule on POST /users/register will not count account creations. Note the app-level throttle/Turnstile options instead.

* Document current Cloudflare free-plan edge controls

Record the production setup: Cloudflare-only Caddy origins, Bot Fight Mode, and the 10-second login flood rule (10 POSTs per 10 seconds, 10-second block). Clarify that the application's 15-minute throttle remains the real credential lockout.

* Auto-refresh Cloudflare CIDRs for Caddy

Move the origin allowlist into a generated cloudflare-ranges.caddy imported by Caddy. Add an hourly systemd timer and script that fetch Cloudflare's v4/v6 lists, reject malformed responses, validate the candidate Caddyfile, and reload Caddy only when the ranges change. Restore the previous file on validation or reload failure.

* Document Cloudflare CIDR refresher setup and operations

Record the installed paths, permissions, timer checks, manual run, update procedure, and the direct-on-VPS setup fallback when the deploy directory is absent.
2026-11-11 21:27:59 +01:00

40 lines
1.0 KiB
Elixir

defmodule Chesstrainer.Accounts.Role do
@moduledoc """
The ordered authority tiers a user can hold.
A higher rank may do everything a lower rank may, so authorization checks
should ask for the minimum tier they need via `at_least?/2`.
"""
@type value :: :member | :moderator | :admin | :super_admin
@values [:member, :moderator, :admin, :super_admin]
@ranks %{
member: 0,
moderator: 1,
admin: 2,
super_admin: 3
}
@doc "All roles, ordered from least to most authority."
def values, do: @values
@doc "The numeric rank of a role."
def rank(role) when role in @values, do: Map.fetch!(@ranks, role)
@doc """
Returns true when `role` is at least as authoritative as `minimum`.
A missing role (no user) never satisfies any minimum.
"""
def at_least?(role, minimum) when role in @values and minimum in @values do
rank(role) >= rank(minimum)
end
def at_least?(_role, _minimum), do: false
@doc "Returns true when the role may use the admin area."
def admin?(role), do: at_least?(role, :admin)
end