Menu

Day 24: The Three Axes of Permissions: Action, Row and Column
πŸ“°

Day 24: The Three Axes of Permissions: Action, Row and Column

DEV Community: dotnetΒ·Jeff TsaiΒ·about 2 hours ago
#1z3p5PQe
#devtodotnet#devto#dev#column#action
Reading 0:00
15s threshold

The API Payload Security Pipeline: Order, Protection Levels and Keys closed by changing axis. A protection level governs the form of one call, and at no point does it ask which data this person may see.

Permissions are something an ERP system cannot avoid, and they have never been one question. They are three: whether a buyer may delete a purchase order, which orders may be deleted, and whether the cost column on that order can be seen at all, or changed. The three answers come from different sources, and they are enforced in different places.

This post covers:

What X-Api-Key and Authorization each answer, and why neither of them is a permission

Where the action axis is granted, and why a form that declares nothing skips the whole thing

Who declares the scope on the row axis, how it becomes one SQL statement, and why assembling it never queries the database

Why the column axis exists only on the front end, and why it is not bound to the same permission model

1.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.