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

请教一下,升级后oather一直报401 #20

Closed
zengjuemin opened this issue Jan 8, 2019 · 5 comments
Closed

请教一下,升级后oather一直报401 #20

zengjuemin opened this issue Jan 8, 2019 · 5 comments

Comments

@zengjuemin
Copy link

我新下了代码后,在用postman进行http://localhost:9030/uaa/oauth/token时status=401,有人能说一下吗

@yangxiufeng666
Copy link
Owner

@zengjuemin 表oauth_client_detail下的client_secret用BCryptPasswordEncoder加密一下。

@zengjuemin
Copy link
Author

关于上述问题,在fank 帮助下,已经解决了,主要原因就是这一次升级后数据库脚本发生很大变化,原来rc_开头的表,全部换成sys_开头了,另外,原来oauth_client_details 表 webApp那条记录密码由原来的webApp换成123456再加密的!在此感谢fank,同时在这里也提出下一个问题就是monitor那个工程现在是不是不能用了,一是pom.xml注了zipkin的全部,二是MonitorApplication的注解@EnableZipkinServer出错!
望各位同仁或已解决了朋友,提出指教一下!

@AkiraRex
Copy link

我也遇到了同样的问题,http://localhost:9030/uaa/oauth/token时status=401
但是直接访问授权中心http://localhost:9060/oauth/token时,是可以正确返回token的,
请问是什么问题呢

@yangxiufeng666
Copy link
Owner

@AkiraRex
zuul会过滤点敏感的Header,不会下发到后面的服务,需要打开
zuul:
routes:
uaa:
sensitiveHeaders:

@AkiraRex
Copy link

非常感谢,我已经发现是这个问题了。谢谢

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

No branches or pull requests

3 participants