mirror of
https://github.com/penpot/penpot.git
synced 2026-11-01 07:20:32 +00:00
8853445951
Operators get a full instance administration panel behind a new
"superuser" access rule. The :app.auth/superusers service resolves
the configured :superusers emails to profile ids once at startup,
so guarded calls are a plain contains? with no query. A token
carrying "superuser" as an operator-granted scope also passes, for
automation without a session; tokens are created with empty perms,
so this opens nothing by itself.
The check is a branch of wrap-authentication, after auth and
before params validation, so outsiders get 403
:superuser-required without leaking expected params. Other token
scopes keep their exact meaning. get-profile and the login
response report the same answer as :is-superuser; the team-scoped
:is-admin is untouched. On devenv any authenticated profile
passes, as the /dbg gate does. The :admins config becomes
:superusers (PENPOT_SUPERUSERS) with no compatibility layer:
operators must rename it or instance-admin access fails closed.
Quote notifications go to the same set.
Admin operations live in app.rpc.admin.* behind
/api/admin/methods, with the same auth wrapping as main but
excluded from the main API docs. Profiles can be listed,
inspected, blocked, unblocked, deleted and restored, teams listed
with members and features, projects and files listed with validate
and repair, error reports listed and shared through JWE links,
and the virtual clock read and set.
Delete and restore run as durable jobs on the unified job table:
the command stamps the object's own row inline so it reads back
instantly, then a delete-object or restore-object job walks the
rest of the tree through app.features.object-cascade. Listing
uses created-at cursors over the new 0157 indexes.
The panel itself is a static SPA served under /admin (public like
any asset; the JS gate reads :is-superuser from get-profile)
with dashboard, users, teams, projects, files and error-report
pages. Devenv points /admin at the backend.
Covered by backend-tests rpc-superuser-test plus
rpc-admin-{users,teams,project,file,delete,restore,misc,
error-reports,error-share} and http-admin tests, with green
regressions on profile, auth and quotes.
Relates to #12015
AI-assisted-by: muse-spark-1.3-contributor
41 lines
1.4 KiB
JavaScript
41 lines
1.4 KiB
JavaScript
// Session gate against the current contract: the product
|
|
// `get-profile` (public, so anonymous callers get an answer too)
|
|
// carries `:is-superuser` when there is a session. It lives on the
|
|
// main API, hence `rpcMain`. JSON responses use camelCase, hence
|
|
// `isSuperuser`. `:is-admin` is team membership and means nothing
|
|
// here.
|
|
|
|
import { rpcMain } from "./api.js";
|
|
|
|
const ANONYMOUS_ID = "00000000-0000-0000-0000-000000000000";
|
|
|
|
// Login hop for a dead session (deleted profile, expired cookie):
|
|
// the product login lives at the deployment root (`<root>/`), next
|
|
// to the panel mount (`<root>/admin/`). It anchors on this module's
|
|
// own url — panel scripts always live at `<root>/admin/js/`, so two
|
|
// levels up is `<root>/` in every deployment (root or subpath) and
|
|
// from any page depth. Returns path plus query (a bare pathname
|
|
// would drop the screen). `moduleUrl` defaults to this file; tests
|
|
// pass their own url.
|
|
export function loginUrl(moduleUrl = import.meta.url) {
|
|
const url = new URL("../../?screen=auth-login", moduleUrl);
|
|
return url.pathname + url.search;
|
|
}
|
|
|
|
export async function checkSuperuserSession() {
|
|
let profile;
|
|
try {
|
|
profile = await rpcMain("get-profile", {});
|
|
} catch (err) {
|
|
if (err.status === 401) {
|
|
return "anonymous";
|
|
}
|
|
throw err;
|
|
}
|
|
|
|
if (!profile || !profile.id || profile.id === ANONYMOUS_ID) {
|
|
return "anonymous";
|
|
}
|
|
return profile.isSuperuser === true ? "superuser" : "denied";
|
|
}
|