vienalatina/apps/board/auth.py
Claude 724dada3f4
Brand Gitea's auth screens, and stop Salir overstating itself
Two halves of the same complaint: the journey into the members area does not
feel like one platform.

Members sign in to /comunidad/ through Gitea, so Gitea's sign-in form and
authorize dialog are part of everyone's journey, not just of anyone who opens a
repository. That is what the earlier "is Gitea only for admins?" question got
wrong. Unthemed they are two dark screens in the middle of a cream site.

Unlike Decap, Gitea supports being themed, so this needs no forking and nothing
a release can silently undo. The repository holds only the colour overrides;
scripts/gitea-theme.sh concatenates them onto the light theme it reads out of
the running container. Keeping somebody else's stylesheet in here would go
stale and turn every Gitea upgrade into a merge — the script is re-run instead,
which is one line in the upgrade notes. Getting a variable name wrong leaves a
corner grey rather than breaking a page, which is the failure mode worth having
when the names belong to someone else's project.

The logo is the site's wordmark, as live text in the same font stack rather than
traced to paths: the site loads no webfont at all, deliberately, so visitors
already see it in whatever sans-serif their machine substitutes. Paths would
render a Montserrat most people never see on the site itself.

Salir was the sharper problem. It cleared this session and the stored token, and
then said "Sesión cerrada" — while the Gitea session in the same browser stayed
open and Gitea still remembered the authorisation, so one click signed the next
person straight back in with no password. On a laptop shared around an
association, that button was lying.

It cannot be fixed from here. Gitea's logout has been POST-only since 1.11.2, so
a link cannot trigger it and a cross-site POST needs a CSRF token this app does
not have; prompt=login is undocumented in every released version of Gitea's
OAuth2 provider, and a security control should not rest on that. So the logout
page now says exactly what is closed and what is not, and links to the one place
that finishes it. Being honest about a limit beats a reassuring message that is
false.

Verified: 101 checks, two of them new — logout warns rather than redirecting,
and leaves no token the server could still act with. The theme itself is
visual and has to be looked at; docs/server-setup.md §12 says where.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NizVpJ2dwzCbjCrTLCjeHn
2026-09-25 16:28:10 +00:00

156 lines
6.0 KiB
Python

"""Sign-in through Gitea.
The rule this module exists to enforce: **a Gitea account is not a membership.**
Gitea answers "who is this person"; the members table answers "may they be
here". Conflating the two would admit every account on the instance, including
the `vienalatina-translations` bot, and would mean anyone who ever gets a Gitea
account for an unrelated reason silently gains access to the board.
"""
from __future__ import annotations
import secrets
from flask import (Blueprint, current_app, flash, g, redirect, render_template,
request, session, url_for)
from . import gitea, tokens
from .db import get_db
bp = Blueprint("auth", __name__)
def redirect_uri() -> str:
return current_app.config["BASE_URL"].rstrip("/") + url_for("auth.callback")
def load_member() -> None:
"""Attach the signed-in member to `g`, or None. Runs on every request.
The role is read from the database each time rather than cached in the
session, so demoting or deactivating somebody takes effect on their next
click instead of whenever their cookie happens to expire.
"""
g.member = None
member_id = session.get("member_id")
if member_id is None:
return
row = get_db().execute(
"""SELECT * FROM members
WHERE id = ? AND active = 1 AND role IN ('owner', 'admin', 'user')""",
(member_id,),
).fetchone()
if row is None:
session.clear()
return
g.member = row
@bp.route("/login")
def login():
if g.member is not None:
return redirect(url_for("board.threads"))
return render_template("login.html", next=request.args.get("next", ""))
@bp.route("/login/start")
def start():
# State ties the callback to this browser session; without it, an attacker
# can feed you their own authorization code and log you into their account.
state = secrets.token_urlsafe(24)
session["oauth_state"] = state
session["oauth_next"] = request.args.get("next", "")
return redirect(gitea.authorize_url(state, redirect_uri()))
@bp.route("/auth/callback")
def callback():
expected = session.pop("oauth_state", None)
given = request.args.get("state")
if not expected or not given or not secrets.compare_digest(expected, given):
flash("El inicio de sesión no se pudo verificar. Inténtalo de nuevo.", "error")
return redirect(url_for("auth.login"))
code = request.args.get("code", "")
if not code:
flash("Gitea no devolvió un código de autorización.", "error")
return redirect(url_for("auth.login"))
try:
credentials = gitea.exchange_code(code, redirect_uri())
profile = gitea.fetch_user(credentials["access_token"])
except gitea.GiteaError as exc:
current_app.logger.warning("OAuth failed: %s", exc)
flash(str(exc), "error")
return redirect(url_for("auth.login"))
except Exception: # network trouble, malformed JSON, Gitea down
current_app.logger.exception("OAuth failed unexpectedly")
flash("No se pudo contactar con Gitea. Inténtalo más tarde.", "error")
return redirect(url_for("auth.login"))
login_name = (profile.get("login") or "").strip()
db = get_db()
member = db.execute(
"""SELECT * FROM members
WHERE gitea_login = ? AND active = 1 AND role IN ('owner', 'admin', 'user')""",
(login_name,),
).fetchone()
if member is None:
# Says nothing about whether the account exists, is inactive, or was
# never a member: an outsider who reaches this page learns only that
# they are not in.
current_app.logger.info("Rejected sign-in for non-member %r", login_name)
flash("Tu cuenta no tiene acceso a esta área. Pide a un administrador que te dé de alta.",
"error")
return redirect(url_for("auth.login"))
db.execute(
"""UPDATE members
SET display_name = ?, email = ?, last_seen_at = datetime('now')
WHERE id = ?""",
(profile.get("full_name") or login_name, profile.get("email") or "", member["id"]),
)
# A fresh session id on privilege change, so a cookie captured before login
# is not still valid after it.
session.clear()
session["member_id"] = member["id"]
# Kept so the editor can commit as this person rather than as a bot. Stored
# in the database, never in the cookie — see apps/board/tokens.py.
tokens.save(member["id"], credentials)
target = request.args.get("next") or session.pop("oauth_next", "") or ""
# Only ever redirect within this app: an absolute URL here would make the
# login page an open redirect that phishing can point anywhere.
if not target.startswith(current_app.config["URL_PREFIX"] + "/"):
target = url_for("board.threads")
return redirect(target)
@bp.route("/logout", methods=["POST"])
def logout():
# Drop the Gitea token too. Signing out should stop the server being able to
# act as you, not just stop the browser being able to ask it to.
if g.member is not None:
tokens.forget(g.member["id"])
session.clear()
# Deliberately NOT a redirect back to the login page.
#
# Clearing this session does not touch the Gitea session in the same
# browser, and Gitea remembers that this app was authorised. So the next
# click on "Entrar con Gitea" gets a code back immediately and signs the
# person straight back in without a password — which on a laptop shared
# around an association means "Salir" was telling them something untrue.
#
# Gitea cannot be signed out from here: its logout has been POST-only since
# 1.11.2, and a cross-site POST would need Gitea's CSRF token. `prompt=login`
# would be the other way round it, and is undocumented in every released
# version of Gitea's OAuth2 provider — not something to rest this on.
#
# So the honest thing is to say so and point at the one place that can
# finish the job.
return render_template("logged_out.html", gitea_url=current_app.config["GITEA_URL"].rstrip("/"))