Business analysis glossary
Authentication and Authorisation
What it is
Authentication confirms who a user or system is, for example by password, one time code or token. Authorisation decides what that authenticated user or system is allowed to do, such as view, create or approve. In HTTP APIs, failing authentication usually returns 401 and failing authorisation returns 403.
Why it matters
Mixing the two up leads to security gaps, such as logged in users seeing other customers' data. Analysts must write access rules as clear requirements: which roles can see or do what, under which conditions, and what message is shown when access is refused.
Example
In the claims portal, an agent logs in with a password and a one time code, which is authentication. The system then allows agents to view claims only for their own branch and allows supervisors to approve claims up to five lakh rupees, which is authorisation. A request for another branch's claim returns 403.