Building Microservices API in Go - Refresh Token: Introduction

The video tutorial explains the concept of refresh tokens, their functionality, and why they are used. It covers the process of obtaining access tokens through authentication, the short-lived nature of access tokens, and the user experience issues caused by expired tokens. The tutorial introduces refresh tokens as a solution to generate new access tokens without requiring frequent logins. It also discusses security measures to prevent token leakage and manage refresh tokens effectively. The video concludes with a preview of generating refresh tokens in the login API.

What is the primary role of the auth server in the access token flow?

• To provide user interface for login

• To manage user sessions

• To verify client credentials and issue tokens

• To store user credentials

Why is it problematic to have short-lived access tokens without refresh tokens?

• It increases server load

• It requires frequent user logins

• It complicates token storage

• It reduces security

How does a refresh token differ from an access token?

• It is used for initial login

• It is shorter-lived

• It is long-lived and used to obtain new access tokens

• It is stored on the server

What is a potential risk if a refresh token is leaked?

• The user will be logged out

• A hacker can generate new access tokens

• The access token will expire immediately

• The auth server will shut down

What is the purpose of a refresh token store?

• To log user activities

• To keep track of user sessions

• To store user credentials securely

• To manage and validate refresh tokens