apache / incubator-seata

:fire: Seata is an easy-to-use, high-performance, open source distributed transaction solution.
https://seata.apache.org/
Apache License 2.0
25.25k stars 8.77k forks source link

k8s部署seata #6593

Open zxz-ai opened 4 months ago

zxz-ai commented 4 months ago

18:11:05.527 ERROR --- [ http-nio-7091-exec-10] [ty.JwtAuthenticationEntryPoint] [ commence] [] : Responding with unauthorized error. Message - Full authentication is required to access this resource 18:11:05.536 ERROR --- [ http-nio-7091-exec-1] [ty.JwtAuthenticationEntryPoint] [ commence] [] : Responding with unauthorized error. Message - Full authentication is required to access this resource

zxz-ai commented 4 months ago

这个问题怎么解决呀 k8s部署完seata后 访问报错 需要身份验证 tokenValidityInMilliseconds: 1800000 设置了过去时间了 ignore: urls: /,//*.css,/*/.js,//*.html,//*.map,/*/.svg,//*.png,/*/.ico,/console-fe/public/**,/api/v1/auth/login

liuqiufeng commented 4 months ago

是访问console时报的错吗?目前console默认打开首页并检查是否登录过,如果未登录则会出现以上日志,此时前端页面应当跳转到了登录页,是正常现象。

Is it an error when accessing the console? Currently, the console opens the homepage by default and checks whether you have logged in. If you haven't logged in, the above log will appear. At this time, the front-end page should have redirected to the login page, which is a normal occurrence.

zxz-ai commented 4 months ago

是重定到登陆页面了 不过还是报这个错误 访问控制台没有出错 就是在pod日志中有这个错误

liuqiufeng commented 4 months ago

是重定到登陆页面了 不过还是报这个错误 访问控制台没有出错 就是在pod日志中有这个错误

正常登录后,不应该再出现此错误。 After logging in normally, this error should not occur again.

zxz-ai commented 4 months ago

seata 可以正常登陆 pod中报 http-nio-7091-exec-2] [ty.JwtAuthenticationEntryPoint] [ commence] [] : Responding with unauthorized error. Message - Full authentication is required to access this resource

liuqiufeng commented 4 months ago

seata 可以正常登陆 pod中报 http-nio-7091-exec-2] [ty.JwtAuthenticationEntryPoint] [ commence] [] : Responding with unauthorized error. Message - Full authentication is required to access this resource

正常登录成功后应该就不会出现了,目前是登录成功之后的请求也还在出现此错误吗? After a successful login, this error should not occur. Is this error still present in requests that have been successfully logged in?

zxz-ai commented 4 months ago

是的 登陆成功请求pod中还是报这个错误

zxz-ai commented 4 months ago

image

xingfudeshi commented 3 months ago

@liuqiufeng PTAL