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

etcdv3 how to send an authdisable request through api #7293

Closed
xjjy1083 opened this issue Feb 9, 2017 · 11 comments
Closed

etcdv3 how to send an authdisable request through api #7293

xjjy1083 opened this issue Feb 9, 2017 · 11 comments

Comments

@xjjy1083
Copy link

xjjy1083 commented Feb 9, 2017

Bug reporting

A good bug report has some very specific qualities, so please read over our short document on
reporting bugs before you submit your bug report.

To ask a question, go ahead and ignore this.

@xiang90
Copy link
Contributor

xiang90 commented Feb 9, 2017

I do not understand this question. Can you please be more specific?

@xjjy1083
Copy link
Author

xjjy1083 commented Feb 9, 2017

etcdv3: Can you please provide more details about how to pass token in header during an authdisable request?

@xiang90
Copy link
Contributor

xiang90 commented Feb 9, 2017

What header? Are you trying to use HTTP API instead of gRPC?

@xjjy1083
Copy link
Author

xjjy1083 commented Feb 9, 2017

Yes, HTTP API.Where should i place token?In header?

@xiang90
Copy link
Contributor

xiang90 commented Feb 9, 2017

@mitake I do not think HTTP gateway works well for v3 auth, right?

@heyitsanthony
Copy link
Contributor

@xiang90 people have asked about it in the past, we should probably doc how to use auth with the grpc gateway since it's not obvious at all (fiddling with http headers to populate the metadata?)

@xiang90
Copy link
Contributor

xiang90 commented Feb 9, 2017

@heyitsanthony I am not sure if it can even work... I will give it a try over this week though.

@mitake
Copy link
Contributor

mitake commented Feb 9, 2017

@xiang90 @heyitsanthony @xjjy1083 currently proxies cannot work with auth, it is a swagger matter: #6643 (comment)

It seems that some people need the feature. After finishing the jwt support, I would be able to allocate a time for it if no one works on it at the time. But if someone can find a way of configuring metadata in swagger, it will be very helpful.

@brkyn
Copy link

brkyn commented Feb 9, 2017

I just encounter the same problem.
Is there a workaround? OR we must use gRPC currently?
Thx!

@mitake
Copy link
Contributor

mitake commented Feb 9, 2017

@brkyn Could you use clientv3 package directly for now? It is an only way for using auth in v3 API.

@xiang90
Copy link
Contributor

xiang90 commented Feb 12, 2017

this is a dup with #6643 Let's track the issue there. Closing.

@xiang90 xiang90 closed this as completed Feb 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

5 participants