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

建议把micro v2 的auth引入 #66

Open
LayneGuo opened this issue Dec 22, 2020 · 6 comments
Open

建议把micro v2 的auth引入 #66

LayneGuo opened this issue Dec 22, 2020 · 6 comments

Comments

@LayneGuo
Copy link

No description provided.

@printfcoder
Copy link
Member

好,安排,会作调整后迁入。期待在下一版本面世

@printfcoder
Copy link
Member

已完成,择期发布:#69

@LayneGuo
Copy link
Author

已完成,择期发布:#69

go-micro会对请求拦截,做权限认证。但stack-rpc好像漏掉了这个

@printfcoder
Copy link
Member

已完成,择期发布:#69

go-micro会对请求拦截,做权限认证。但stack-rpc好像漏掉了这个

拦截?是指网关层做这事吗,我记得auth只是一个认证库,还没有在每个调用之间进行验证的。

@LayneGuo
Copy link
Author

LayneGuo commented Jan 3, 2021

已完成,择期发布:#69

go-micro会对请求拦截,做权限认证。但stack-rpc好像漏掉了这个

拦截?是指网关层做这事吗,我记得auth只是一个认证库,还没有在每个调用之间进行验证的。

go-micro在client->server的rpc调用的时候可以 Inspect& verify

@printfcoder
Copy link
Member

已完成,择期发布:#69

go-micro会对请求拦截,做权限认证。但stack-rpc好像漏掉了这个

拦截?是指网关层做这事吗,我记得auth只是一个认证库,还没有在每个调用之间进行验证的。

go-micro在client->server的rpc调用的时候可以 Inspect& verify

wrapper 包装的那些call、trace?打算做成可配置的,默认不打开,而不是强制都wrapper,很多团队内部其实是不需要这些的。

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

2 participants