Authentication & Authorization.

Refresh Token

Routes

Login user

- When a new user is created, his credentials are stored in a common token and his session is in a token called refresh-token, in which is only the e-mail or id of the session owner (user).

• The common token is returned in the body of the response and the refresh-token is sent by the cookie, which is automatically saved by the browser (by configuring the feth or axios module).

userRoutes.post(
  '/login',
  AuthMiddleware,
  dtoValidator(LoginUserDto, 'BODY'),
  HttpAdapter(UserController.create, 'add-user-infos'),
);

Refresh Token

- In this route, the user's session token ( refresh-token ) is checked if it is still valid, if it is valid, a new common token is generated and returned in the server's response.

• Your session is automatically sent in the cookie to the server by the module used in the front-end ( fetch or axios ).

userRoutes.post(
  '/refresh-token',
  RefreshTokenMiddleware,
  HttpAdapter(UserController.refreshToken, 'add-user-infos'),
);

Auth Context

• The user common token is saved in memory (variable or state) in the browser. Whenever the user reloads the page, a new request is made to the back-end accessing the refres-token route sent to the session by the cookie. If the session is still valid, a new short-lived token is returned.

export const AuthContextProvider = function ({ children }) {
  const [Token, setToken] = React.useState(false);

  useEffect(() => {
    if (!Token) {
      async function RefreshToken() {
        const response = await UserService.refreshToken();

        setToken(response.token);
      }

      RefreshToken();
    }
  }, []);

  return (
    <AuthContext.Provider value={{ Token, setToken }}>
      {children}
    </AuthContext.Provider>
  );
};