authorization

Deciding whether an already identified caller may perform a particular action on a particular resource.

In more detail

It follows authentication and is checked by the service that owns the resource, even if a gateway already verified the token. A known caller without permission gets 403 Forbidden. Field selection, filters and embedded data must all respect it, and it should deny by default when facts are missing.

Examples

In AWS: Deciding what an already identified caller is allowed to do.
sudo: bob : user NOT in sudoers ; TTY=pts/1 ; PWD=/home/bob ; USER=root ; COMMAND=/usr/bin/cat /etc/shadow
09:15:10 bob     authz refused as root: /usr/bin/cat /etc/shadow
It comes after authentication: once a system knows who you are, file modes, sudo rules or an application's own checks decide what you may do. A valid TLS certificate or accepted SSH host key proves an identity but grants nothing by itself. Server-side authorization, such as an authorized_keys entry, is what actually admits a user.
The course calls it a design problem, fixed by putting the ownership check inside the data lookup and taking the caller's rights from the server, never from the request.

Related terms

Taught in

References

Certification courses