# Http\_poller and auth tokens

**URL:** <https://discuss.elastic.co/t/http-poller-and-auth-tokens/102771>\
**Category:** Logstash\
**Created:** [October 4, 2017, 10:32pm UTC](https://discuss.elastic.co/t/http-poller-and-auth-tokens/102771 "2017-10-04T22:32:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rsk0](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rsk0/32/124810_2.png) [@rsk0](https://discuss.elastic.co/u/rsk0)\
**Post date:** [October 4, 2017, 10:32pm UTC](https://discuss.elastic.co/t/http-poller-and-auth-tokens/102771/1 "2017-10-04T22:32:48Z")

</div>

I've got a scenario where using an auth token would be preferred over basic auth. I know http\_poller doesn't handle this currently, but do you think it might be possible in the future?

I suppose one big challenge is the variety of methods APIs use for providing and accepting auth tokens, which makes this problem resemble the previously discussed pagination issue ([Response Headers http\_poller](https://discuss.elastic.co/t/response-headers-http-poller/80739)), and so it looks intractable.

What about allowing for pre- and post-query arbitrary Ruby, with the ability to read from and modify plugin state and HTTP headers?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 1, 2017, 10:32pm UTC](https://discuss.elastic.co/t/http-poller-and-auth-tokens/102771/2 "2017-11-01T22:32:51Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.