What to look for
Authentication and authorisation
Who the user is, and what the user may do.
0 of 7 completed
- 1Signing in
Signing in is how a website checks who a person is. The lesson reviews the sign-in code of a sports shop and explains a second proof at sign-in.
Open the lesson
Listen to an AI summary of Signing in
0:00 / 0:34 - 2Sessions
After sign-in a server gives the browser a session id in a cookie, which says who sent each later request. The lesson covers how a session id is made, sent and ended.
Open the lesson
Listen to an AI summary of Sessions
0:00 / 0:31 - 3Signed tokens
Some applications put a signed token in the cookie in place of a session id. The lesson covers what a JSON Web Token holds and the checks a server makes on a token.
Open the lesson
Listen to an AI summary of Signed tokens
0:00 / 0:37 - 4OAuth and OpenID Connect sign-in
A website can let a person sign in with an account from another company. The lesson covers the four checks that sign-in needs.
Open the lesson
Listen to an AI summary of OAuth and OpenID Connect sign-in
0:00 / 0:39 - 5Password reset
A website lets a person who forgets a password choose a new one. The lesson follows a reset in the sports shop and shows how a reset link can lead to an attacker.
Open the lesson
Listen to an AI summary of Password reset
0:00 / 0:32 - 6Object references
A website that fetches an order by number must check who the order belongs to. A second weakness lets a customer change a value the website never asked for.
Open the lesson
Listen to an AI summary of Object references
0:00 / 0:31 - 7Function level checks
A website has actions that only some people may use, such as deleting a user. The lesson shows the check that protects an action and the code with the check missing.
Open the lesson
Listen to an AI summary of Function level checks
0:00 / 0:33