REST APIs with Flask and Python - What is a Fresh Token?

The video tutorial explains the concept of token freshness, focusing on the difference between fresh and non-fresh tokens. It discusses scenarios where fresh tokens are required, such as critical operations like password changes, and how tokens can be refreshed using Flask JWT extended. The tutorial emphasizes the importance of fresh tokens in ensuring security and user identity verification.

What is the primary purpose of a fresh token in a REST API?

• To provide faster browsing speeds

• To allow unlimited access to all resources

• To store user preferences

• To ensure the user is who they claim to be during critical operations

How does a website typically handle an expired token?

• It blocks the user from accessing the site

• It logs the user out immediately

• It asks the user to create a new account

• It refreshes the token using existing information

What happens when a fresh token expires?

• The user must re-enter their username and password

• The user is logged out

• A new fresh token is automatically issued

• The token is refreshed to a non-fresh token

Why might a website ask for your password again when changing your password?

• To log the user out

• To reset the user's session

• To ensure the user is still the same person

• To update the password in the database

In what scenario is a fresh token particularly important?

• When browsing non-sensitive pages

• When accessing public content

• When performing critical operations like password changes

• When logging out

What is a non-fresh token?

• A token that never expires

• A token that requires a password every time

• A token generated from refreshing a previous token

• A token that allows access to all site features

What is the main difference between a fresh token and a non-fresh token?

• Non-fresh tokens never expire

• Non-fresh tokens are generated from refreshing

• Fresh tokens are issued without user credentials

• Fresh tokens are only used for logging out