Protocols
Saved & recent

Authorization

Also called: authz, access control

Authorization determines what an entity is allowed to do with a resource. A decision can depend on identity, assigned roles, requested action, resource ownership, and other context. Permissions should be enforced where the resource is accessed, not merely by hiding controls in a user interface.

For example, the same authenticated developer may read a repository but be denied permission to delete it. A service must evaluate the requested operation against its policy. Some resources also allow anonymous access, so authorization decisions need not always follow a named-user login.

Related
Authentication, OAuth 2.0, Mutual TLS
Further reading
RFC 4949 — Internet Security Glossary, Version 2
developer authenticated identity repository policy read: allow delete: deny ALLOWED DENIED read repository delete repository one identity · two action decisions
Hypothetical repository policy: the same authenticated developer can read but cannot delete. Authorization evaluates the requested action on the resource; hiding a delete button does not enforce this policy.

View in the full Protocols collection