如何在react中使用刷新令牌

问题描述 投票:0回答:1

我想使用刷新令牌在反应应用程序中获取新的访问令牌。我向 API 发送请求以获取有关书籍的数据。如果我收到 401 或 500 错误,我想使用刷新令牌向另一个 API 发送请求,以获取新的访问令牌,然后发送到第一个 API 以获取有关图书的数据。 在这里,我首先使用 2 useEffect 来获取书籍数据,然后使用 2 个 useEffect 来获取新的访问令牌。我还有一个 setInterval 来运行第一个 useEffect 来获取书籍数据。如果我更改本地存储中的访问令牌并故意使其崩溃以手动获取 401 错误,我希望来自刷新令牌的新访问令牌使本地存储中的访问令牌再次正确,从而阻止页面崩溃。所以我的问题是两件事:首先我不这样做知道如何处理我的新 accesstoken 。第二个是当我更改 localStorage 中的 accesstoken 以手动获取 401 错误时,如果我刷新页面,我希望我的 localStorage 设置新的访问令牌,以便页面不会崩溃。 这是我的 useContext 和处理这两个 useEffects 的组件:

这是我的 useContext 挂钩:

import React from "react";
import { useState } from "react";

const AuthContext = React.createContext({
 token: "",
 refreshToken: "",
 isLoggedIn: false,
 login: () => {},
 logout: () => {},
 booksData: [],
  });

export const AuthContextProvider = (props) => {
  let initialToken = localStorage.getItem("token");
  let initialRefreshToken = localStorage.getItem("refresh-token");
  const [token, setToken] = useState(initialToken);
  const [refreshToken, setRefreshToken] = useState(initialRefreshToken);
  const isUserLoggedIn = !!token;

  const logoutHandler = () => {
   setToken(null);
   localStorage.removeItem("token");
   localStorage.removeItem("books");
   localStorage.removeItem("refresh-token")};

  const loginHandler = (token, refreshToken) => {
   setToken(token);
   setRefreshToken(refreshToken);
   localStorage.setItem("token", token);
   localStorage.setItem("refresh-token", refreshToken);
   };

 const contextValue = {
   token,
   isLoggedIn: isUserLoggedIn,
   refreshToken,
   login: loginHandler,
   logout: logoutHandler,
  };

 return (
   <AuthContext.Provider value={contextValue}>
    {props.children}
   </AuthContext.Provider>
  );
};
export default AuthContext;

这是我的组件:

  const Books = () => {
    const ctx = useContext(AuthContext);
    const [books, setBooks] = useState([]);
    const [reqCounter, setReqCounter] = useState(0);
    const [tokenError, setTokenError] = useState(false);

   useEffect(() => {

     const fetchData = async () => {
       let response = await fetch("some API endpoint", {
       method: "GET",
       headers: {
          Authorization: `Bearer ${ctx.token}`,
        },
  });
  try {
    const data = await response.json();
    if (response.status === 200) {

      setBooks(data.books);
    } else if (response.status === 404) {
      setError("No page found");
    } else if (response.status === 403) {
      setError("You dont have accsess to this page");
    }
  } catch (error) {
    setTokenError(true);
  }
};
fetchData();
}, [ctx.token, reqCounter, ctx]); // Is my dependencies right??

 setInterval(() => {
   setReqCounter(reqCounter + 1);
}, 5000);

 useEffect(() => {
   const refresh = async () => {
   const response = await fetch("some API", {
      method: "POST",
      body: JSON.stringify({
      refresh_token: ctx.refreshToken,
    }),
    headers: {
      "Content-Type": "application/json",
    },
  });
  const data = await response.json();
  if (response.ok) {
     // Dont Know what should I write here!
  }
};
  refresh();
  }, [tokenError]); // Is my dependencies right??

const content = books.map((item) => (
  <BookItem
    title={item.name}
    year={item.publish_date}
    pages={item.pages}
    author={item.Author}
    img={item.thumbnail}
    key={item.name}
  />
));
return (
  <section className={classes.bookPage}>
    {!error && books.length !== 0 && (
    <ul className={`list ${classes.booksList}`}>{content}</ul>
    )}
    {error && <h2 className={classes.error}>{error}</h2>}
    {isLoading && <PulseLoader color="#f53e3e" className={classes.spinner} />}
  </section>
);
  };

  export default Books;
reactjs react-hooks token refresh-token
1个回答
1
投票

建议

理想情况下,在一个地方处理带有令牌的获取和令牌刷新,例如 HttpContext 但要检查您可以从现有的 authcontext 开始

您可以定期刷新令牌 或者当未经授权的来电时

问题:

  • 当token过期后,某些调用会失败,需要使用新的token重新进行
  • 定期刷新 token 时,如果旧 token 失效,队列中使用旧 token 的某些调用可能会失败

伪代码

 in AuthContext 

 const fetchData = async (link) => {
   try {
   let response = await fetch(link, {
   method: "GET",
   headers: {
      Authorization: `Bearer ${token}`,
    },
   });
    
   } catch(error) {
      // check status and attempt refresh
      // but existing calls will old token will fail,
      // can will cause multiple refresh token to be called
   }

 }

 //or refresh token on regular interval
   useEffect(() => {

    const timerId = setInterval(() => {

        // refresh token and set token
        // The problems is the moment the token is refreshed, the old token might get invalidated and some calls might fail

    }, tokenRefershTimeInMilliSec)

      return () => {
        clearInterval(timerId)
      }

   }, [])

 ...
 const contextValue = {
   token,
   isLoggedIn: isUserLoggedIn,
   refreshToken,
   login: loginHandler,
   logout: logoutHandler,
   get: fetchData
 }; 

 return <AuthContext.Provider value={contextValue} {...props}> // pass all props down

或者使用 http 上下文来分隔关注点

const initalValue = // some value
const HttpContext = React.createContext(initalValue);

const initialToken = // from localstorage

const HttpContextProvider = (props) => {

   const [token, setToken] = useState(initialToken)

   const fetchData = async (link) => {
   try {
   let response = await fetch(link, {
   method: "GET",
   headers: {
      Authorization: `Bearer ${token}`,
    },
   });
    
   } catch(error) {
      // check status and attempt refresh
      // but existing calls will old token will fail,
      // can will cause multiple refresh token to be called
   }

   }

    const value = useMemo(() => {
      return {
       get: fetchData,
       // post, put, delete
    }}, [token]
  
   //refresh token on regular interval
   useEffect(() => {

    const timerId = setInterval(() => {

        // refresh token and set token
        // The problems is the moment the token is refreshed, the old token might get invalidated and some calls might fail

    }, tokenRefershTimeInMilliSec)

      return () => {
        clearInterval(timerId)
      }

   }, [])


   return (<HttpContext.Provider {...props}>)

}

如果您愿意使用 axios,那么您可以检查自动刷新的方式或使用像 axios-auth-refresh

这样的库

希望它能为您指明正确的方向

© www.soinside.com 2019 - 2024. All rights reserved.