authentication

Establishing who a request represents, for example by checking a password, a session cookie or a signed token.

In more detail

Authentication answers who you are; deciding what you may then do is authorization. Common methods are passwords, access tokens, keys and one-time codes.

Examples

In AWS a password, an access key signature or a session token is turned into an IAM identity.
feat(auth)!: require a token on every session endpoint (auth is the scope)
Authentication answers who is this; authorization answers what may they do. On Linux, an account name alone proves nothing: the password check against /etc/shadow, or an SSH key, does the proving. In SSH and TLS, the server first proves its own identity, and user authentication is a separate step afterwards.
The course calls it a library problem, where the classic mistakes are fast password hashes, equality comparisons that leak timing, no limit on login attempts, and session tokens that are guessable or never expire.

Related terms

Taught in

References

Certification courses