b90cbd2a9f
Three complaints, one cause. Logging out could not finish because the session belonged to another server, whose logout is POST-only and unreachable from here. "Ese usuario ya está en uso" for somebody absent from Miembros, because erase_member deleted our row and left the git account standing — two stores of users, one of them showing. And the hand-off to a differently-designed domain, with a Forgot password that could never work. All three followed from delegating identity, so it is no longer delegated. Members now sign in at /comunidad/login against a scrypt hash in our own database, via werkzeug.security, which arrives with Flask. They have no account on the git server at all, which makes the collision impossible rather than fixed. Logout is one click. This removes more than it adds: the OAuth round trip, the client registration, tokens.py with its refresh-before-expiry logic, the gitea_tokens table, and the logged-out page that existed to apologise for a logout that did not log you out. The editor keeps per-writer attribution without per-writer tokens: one CONTENT_TOKEN commits, and each commit names its author, which Gitea's contents API supports and a test now asserts. CONTENT_TOKEN falls back to GITEA_ADMIN_TOKEN so nothing breaks on deploy, but it only needs write access to one repository, while the admin token can modify every account on the instance — and now has no remaining job. The refusals are the interesting part. Unknown name, wrong password, suspended member and invited-but-never-arrived all answer identically, asserted by comparing the rendered bytes. The hash check runs against a decoy even when there is no such member, so an unknown name does not answer faster. Attempts are rate limited, counted inside SQLite for the reason invites.py documents. A NULL hash never matches anything. Migration 2 adds password_hash and drops the dead OAuth tokens. Everyone starts NULL, including the owner, so scripts/set-password.sh exists and was tested before this could ship: it prompts without echo, never takes the password as an argument where ps would show it, and refuses a short one or an unknown member. Rehearsed against a rebuilt copy of the server's database: starts, keeps the photo, drops the tokens table, serves a login form with no redirect, signs in, signs out, stays out. 223 tests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NizVpJ2dwzCbjCrTLCjeHn
42 lines
1.7 KiB
Plaintext
42 lines
1.7 KiB
Plaintext
# Copy to .env next to docker-compose.yml and fill in. Never commit .env.
|
|
#
|
|
# openssl rand -hex 32
|
|
BOARD_SECRET_KEY=
|
|
|
|
# NOT USED ANY MORE. Members sign in on vienalatina.com against a password
|
|
# stored here, so there is no OAuth application and nothing to configure.
|
|
# Leaving these lines in your .env is harmless; the OAuth application itself
|
|
# can be deleted in Gitea.
|
|
#BOARD_OAUTH_CLIENT_ID=
|
|
#BOARD_OAUTH_CLIENT_SECRET=
|
|
|
|
# Gitea username of the first and only owner. Applied once, to an empty
|
|
# database, and ignored afterwards.
|
|
BOARD_OWNER=pablo
|
|
|
|
# Optional. A site-admin token lets admins create Gitea accounts from inside
|
|
# the members area. Without it, everything works except account creation, and
|
|
# admins add people who already have a Gitea login.
|
|
GITEA_ADMIN_TOKEN=
|
|
|
|
# What the content editor commits with. Members sign in here, on
|
|
# vienalatina.com, and have no account on the git server at all — so this is
|
|
# the only credential that touches it, and it only needs `write:repository` on
|
|
# the site repository. Left empty it falls back to GITEA_ADMIN_TOKEN, which
|
|
# works but grants far more than publishing a post requires.
|
|
CONTENT_TOKEN=
|
|
|
|
# Outgoing mail, for invitations and password resets. Without it an admin can
|
|
# still add members, but nobody can be invited and nobody can recover a
|
|
# password — which is the whole reason members could not get in before.
|
|
#
|
|
# These are the SMTP details of the hola@vienalatina.com mailbox. Port 465 means
|
|
# MAIL_SECURITY=ssl; port 587 means starttls. Using the wrong one of the pair is
|
|
# the usual reason a mailbox that works in a mail client fails here.
|
|
MAIL_HOST=
|
|
MAIL_PORT=587
|
|
MAIL_SECURITY=starttls
|
|
MAIL_USER=hola@vienalatina.com
|
|
MAIL_PASSWORD=
|
|
MAIL_FROM=Viena Latina <hola@vienalatina.com>
|