# Apache Reverse Proxy - passing Multifactor authorization back

**URL:** <https://discuss.elastic.co/t/apache-reverse-proxy-passing-multifactor-authorization-back/183166>\
**Category:** Elasticsearch\
**Created:** [May 28, 2019, 6:42pm UTC](https://discuss.elastic.co/t/apache-reverse-proxy-passing-multifactor-authorization-back/183166 "2019-05-28T18:42:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![S\_Chase](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/s_chase/32/33237_2.png) [@S\_Chase](https://discuss.elastic.co/u/S_Chase)\
**Post date:** [May 28, 2019, 6:42pm UTC](https://discuss.elastic.co/t/apache-reverse-proxy-passing-multifactor-authorization-back/183166/1 "2019-05-28T18:42:33Z")

</div>

Has anyone implemented on Apache a reverse proxy - passing credentials back like this does with nginx?

> **[User Impersonation with X-Pack: Integrating Third Party Auth with Kibana](https://www.elastic.co/blog/user-impersonation-with-x-pack-integrating-third-party-auth-with-kibana)**
>
> Looking to use X-Pack security features with an authentication service not covered by one of these built-in realms? You have a couple options.

---

<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:** [June 25, 2019, 6:42pm UTC](https://discuss.elastic.co/t/apache-reverse-proxy-passing-multifactor-authorization-back/183166/2 "2019-06-25T18:42:46Z")

</div>

Closed on June 25, 2019, 6:42pm UTC

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