Skip to content

Atom 10.0.0

Choose a tag to compare

@atom36942 atom36942 released this 17 Nov 07:43
· 46 commits to main since this release

Upgrade (projects must change): Per-user permissions are enforced: a route with user_check_permission: {"mode": "token"} admits only users whose users.permissions holds its id (auth.md). Atom's samples: /admin/postgres-query-runner-write (6) needs role 1 and permission 6; /admin/user-delete (132) needs permission 132 only. Root (id 1) gets both at startup; root logs in again to use them, and other admins need a grant through /admin/user-update.

A project that sets config_column_int_mapping["users"] keeps Atom's labels (startup refuses a permission route without one):

"users": {**base_config_column_int_mapping["users"], "role": {1: "Admin", 2: "General"}},