return FALSE; $r = well_tag_thread__update(array('id' => $id), $update); return $r; } function well_tag_thread_find($tagid, $page, $pagesize) { $arr = well_tag_thread__find(array('tagid' => $tagid), array('id' => -1), $page, $pagesize); return $arr; } function well_tag_thread_find_by_tid($tid, $page, $pagesize) { $arr = well_tag_thread__find(array('tid' => $tid), array(), $page, $pagesize); return $arr; } ?>next.js - When deployed to the cloud, auth.js fails to refresh the access token seemingly at random - Stack Overflow

科技改变生活-雨落星辰 - 所有的伟大,都源于一个勇敢的开始

    最新消息：雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客
    你的位置： 首页>programmer>next.js - When deployed to the cloud, auth.js fails to refresh the access token seemingly at random - Stack Overflow

    next.js - When deployed to the cloud, auth.js fails to refresh the access token seemingly at random - Stack Overflow

    programmeradmin1浏览0评论

    I followed the refresh token rotation JWT strategy on auth.js' website. My JWT is successfully refreshing when I'm developing locally. When I push it live to my Azure web service it also seems to work most of the time. Occasionally, however, even if I left the browser open and running, it will fail to refresh. I see in the backend log the following:

    Error refreshing access token: {
  error: 'invalid_grant',
  error_description: 'Refresh token does not exist (Correlation ID: foo-bar)'

    Could it be that when the container spins down it loses it from the server-side or something?

    继续浏览有关 的文章

    与本文相关的文章

    发布评论

    评论列表(0)

    1. 暂无评论