Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

token合法性问题 #26

Open
skvsang opened this issue Dec 16, 2020 · 2 comments
Open

token合法性问题 #26

skvsang opened this issue Dec 16, 2020 · 2 comments
Labels
question Further information is requested

Comments

@skvsang
Copy link

skvsang commented Dec 16, 2020

jwt生成的token是可以通过绑定的加密算法Hmac直接校验的,为什么要把token存在redis去校验,这样子与其他方案生成加密串作为token有什么区别呢?

@Snailclimb
Copy link
Owner

jwt生成的token是可以通过绑定的加密算法Hmac直接校验的,为什么要把token存在redis去校验,这样子与其他方案生成加密串作为token有什么区别呢?

确实,引入存储就会丧失JWT无状态这个优点。但是,不通过存储服务来保存token,你没办法解决退出登录等场景。

@Snailclimb Snailclimb added the question Further information is requested label Dec 18, 2020
@TestLove
Copy link

TestLove commented Feb 14, 2021

jwt生成的token是可以通过绑定的加密算法Hmac直接校验的,为什么要把token存在redis去校验,这样子与其他方案生成加密串作为token有什么区别呢?

确实,引入存储就会丧失JWT无状态这个优点。但是,不通过存储服务来保存token,你没办法解决退出登录等场景。

如果是这样的话,换用cookie+session是不是会更好一点(因为也将token保存到了服务器中,而且传输的数据量也变大了原本只需要sessionID,现在需要一大串编码字符串)
可以将jwt的过期时间缩短,然后当作一次性凭证使用,使用后即过期

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants