Search for a command to run...
A feature flag can hide a button or route a request to a new code path. It does not decide whether this user may read that customer record.
Treat flags as product rollout controls. After the flag check, still authorize actor + resource + action on the server against the real policy. A flag that turns on "admin tools" for everyone who hits the new build is a privilege bug waiting to ship.
No comments yet. Be the first to comment.
Soft-delete is a data lifecycle choice. Authorization is a security decision. Mixing them up is how tombstoned rows keep answering "yes" long after the product thinks they are gone. The bug pattern A
Most ABAC bugs I see are not bad rules. They are stale inputs. The policy says something like "finance can edit records tagged confidential, but only during business hours." That looks fine in a desig
A common way to wire up an AI agent is to hand it the user's session or OAuth token and let it call APIs "as the user." It's quick, and it feels safe, because the agent can't do anything the user coul
When support or admin tooling mints an impersonation / "act as" token, validating that the operator is allowed to impersonate is only half the check. Every subsequent read and write must still authori
A service-to-service token proves which machine called your API. It does not prove which human may see or change a specific resource. If an internal worker calls GET /invoices/4821 with a service JWT,
Auth By Example
37 posts
