-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
feature: support talking to etcd via TLS. #158
Comments
The TLS authentication for we need to fix this first: openresty/lua-nginx-module#997 |
The TLS authentication is important for auth between end to end, not just for etcd. |
based on this PR: openresty/lua-nginx-module#1599, we can do more things about auth between end to end. |
Hi, I believe that we don't need to support the TLS or the priority of this requirement is not high or even a pseudo-demand. TLS/HTTPS solved the risk of data being hijacked at WAN. APISIX usually access etcd via LAN, and messages in the LAN usually do not need to be considered for hijacking. |
Is there any progress on this issue? TLS communication and mTLS auth ist very important for etcd. |
the official |
OpenResty already support mTLS.
Thanks,
Ming Wen
Twitter: _WenMing
YuanSheng Wang <notifications@github.com> 于2020年8月12日周三 下午11:42写道:
… Is there any progress on this issue?
the official openresty still not support the mTLS now. we have to wait
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#158 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGJZBK7T5QSQ33D6WR6VUD3SAKZ67ANCNFSM4H3N2R3Q>
.
|
We still need to wait more time. |
Solved by #2584 . Server side TLS verification is enough to use by now. |
No description provided.
The text was updated successfully, but these errors were encountered: