NextAuth Hasura 刷新令牌

如何解决NextAuth Hasura 刷新令牌

我正在尝试为 Hasura 身份验证和授权设置 NextAuth。由于 Hasura 需要自定义 jwt 声明,因此我无法使用 OAuth 提供程序提供的默认访问令牌。所以我在 [...nextauth].js 中使用 encode 块来编码自定义 jwt 令牌,一切正常。但我不知道如何为我的自定义令牌实现刷新令牌。下面是我的“pages/api/auth/[...nextauth].js”

import * as jwt from "jsonwebtoken";
import NextAuth from "next-auth";
import Providers from "next-auth/providers";

export default NextAuth({
  providers: [
    Providers.Google({
      clientId: process.env.GOOGLE_CLIENT_ID,clientSecret: process.env.GOOGLE_CLIENT_SECRET,authorizationUrl:
        "https://accounts.google.com/o/oauth2/v2/auth?prompt=consent&access_type=offline&response_type=code",}),],secret: process.env.SECRET,session: {
    jwt: true,},jwt: {
    secret: process.env.SECRET,encode: async ({ secret,token,maxAge }) => {
      const jwtClaims = {
        sub: token.id,name: token.name,email: token.email,picture: token.picture,iat: Date.now() / 1000,exp: Math.floor(Date.now() / 1000) + 60,"https://hasura.io/jwt/claims": {
          "x-hasura-allowed-roles": ["user"],"x-hasura-default-role": "user","x-hasura-role": "user","x-hasura-user-id": token.id,};
      const encodedToken = jwt.sign(jwtClaims,secret,{ algorithm: "HS256" });
      return encodedToken;
    },decode: async ({ secret,maxAge }) => {
      const decodedToken = jwt.verify(token,{ algorithms: ["HS256"] });
      return decodedToken;
    },pages: {
    // signIn: '/auth/signin',// Displays signin buttons
    // signOut: '/auth/signout',// Displays form with sign out button
    // error: '/auth/error',// Error code passed in query string as ?error=
    // verifyRequest: '/auth/verify-request',// Used for check email page
    // newUser: null // If set,new users will be directed here on first sign in
  },// Callbacks are asynchronous functions you can use to control what happens
  // when an action is performed.
  // https://next-auth.js.org/configuration/callbacks
  callbacks: {
    // async signIn(user,account,profile) { return true },// async redirect(url,baseUrl) { return baseUrl },async session(session,token) {
      const encodedToken = jwt.sign(token,process.env.SECRET,{
        algorithm: "HS256",});
      session.token = encodedToken;
      session.id = token.id;
      return Promise.resolve(session);
    },async jwt(token,user,profile,isNewUser) {
      const isUserSignedIn = user ? true : false;
      // make a http call to our graphql api
      // store this in postgres

      if (isUserSignedIn) {
        token.id = profile.id.toString();
      }
      return Promise.resolve(token);
    },// Events are useful for logging
  // https://next-auth.js.org/configuration/events
  events: {},// Enable debug messages in the console if you are having problems
  debug: true,});

有人能告诉我在使用自定义 jwt 令牌时如何使用 next-auth 处理刷新令牌吗?

解决方法

我目前正在使用我在 next-auth 问题页面上的帖子 here 中找到的方法。

本质上,我们使用了 clientMaxAge 选项的组合,您可以传递给提供程序来重新获取会话,从而重新运行 jwt 回调。我不确定我是否正确使用了 keepAlive 属性,但目前看来轮询是正确的,尽管您可能需要对此进行试验。

在您的 JWT 回调中,您可以拥有将检查现有到期时间与另一个逻辑的逻辑,并从您的服务器获取新令牌以分配给会话。

//_app.tsx 
const sessionOptions = {
    clientMaxAge: 60 * 30,// Re-fetch session if cache is older than 30 minutes 
    keepAlive: 60 * 30,// Send keepAlive message every hour
};
<Provider options={sessionOptions} session={pageProps.session}>
  ..
</Provider>

// [...nextauth].ts

const callbacks: CallbacksOptions = {
    async jwt(token: any,user: any) {
        if (user) {
            token.accessToken = user.token;
            token.expires = Date.now() + user.config.USER_SESSION_LENGTH_IN_SECONDS * 1000;
        }

        // Don't access user as it's only available once,access token.accessToken instead
        if (token?.accessToken) {
            const tokenExpiry = token.expires;
            const almostNow = Date.now() + 60 * 1000;

            if (tokenExpiry !== undefined && tokenExpiry < almostNow) {
                // Token almost expired,refresh
                try {
                    const newToken = await api.renewToken(token.accessToken); // calling external endpoint to get a new token
                    // re-assign to the token obj that will be passed into the session callback
                    token.accessToken = newToken.token;
                    token.expires = Date.now() + user.config.USER_SESSION_LENGTH_IN_SECONDS * 1000;
                } catch (error) {
                    console.error(error,'Error refreshing access token');
                }
            }
        }

        return token;
    },async session(session: any,user: any) {
        session.accessToken = user.accessToken;
        session.expires = user.expires;
        return session;
    }
}

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-
参考1 参考2 解决方案 # 点击安装源 协议选择 http:// 路径填写 mirrors.aliyun.com/centos/8.3.2011/BaseOS/x86_64/os URL类型 软件库URL 其他路径 # 版本 7 mirrors.aliyun.com/centos/7/os/x86
报错1 [root@slave1 data_mocker]# kafka-console-consumer.sh --bootstrap-server slave1:9092 --topic topic_db [2023-12-19 18:31:12,770] WARN [Consumer clie
错误1 # 重写数据 hive (edu)&gt; insert overwrite table dwd_trade_cart_add_inc &gt; select data.id, &gt; data.user_id, &gt; data.course_id, &gt; date_format(
错误1 hive (edu)&gt; insert into huanhuan values(1,&#39;haoge&#39;); Query ID = root_20240110071417_fe1517ad-3607-41f4-bdcf-d00b98ac443e Total jobs = 1
报错1:执行到如下就不执行了,没有显示Successfully registered new MBean. [root@slave1 bin]# /usr/local/software/flume-1.9.0/bin/flume-ng agent -n a1 -c /usr/local/softwa
虚拟及没有启动任何服务器查看jps会显示jps,如果没有显示任何东西 [root@slave2 ~]# jps 9647 Jps 解决方案 # 进入/tmp查看 [root@slave1 dfs]# cd /tmp [root@slave1 tmp]# ll 总用量 48 drwxr-xr-x. 2
报错1 hive&gt; show databases; OK Failed with exception java.io.IOException:java.lang.RuntimeException: Error in configuring object Time taken: 0.474 se
报错1 [root@localhost ~]# vim -bash: vim: 未找到命令 安装vim yum -y install vim* # 查看是否安装成功 [root@hadoop01 hadoop]# rpm -qa |grep vim vim-X11-7.4.629-8.el7_9.x
修改hadoop配置 vi /usr/local/software/hadoop-2.9.2/etc/hadoop/yarn-site.xml # 添加如下 &lt;configuration&gt; &lt;property&gt; &lt;name&gt;yarn.nodemanager.res