# Plugin for handling REMOTE\_USER HTTP header?

**URL:** https://meta.discourse.org/t/plugin-for-handling-remote-user-http-header/113947
**Category:** SSO
**Created:** [April 10, 2019, 10:04am UTC](https://meta.discourse.org/t/plugin-for-handling-remote-user-http-header/113947 "2019-04-10T10:04:17Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![BjornW](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bjornw/32/137412_2.png) [@BjornW](https://meta.discourse.org/u/BjornW)
#### Post date: [April 10, 2019, 10:04am UTC](https://meta.discourse.org/t/plugin-for-handling-remote-user-http-header/113947/1 "2019-04-10T10:04:17Z")

</div>

I’m testing out a discourse installation for a customer who uses SAML for all its other logins. However, it doesn’t use just _one_ IDP, but 38. In all the other logins this is handled in two different ways, depending on which is more viable for the site/framework in question:

- Custom-built login site that has all 38 IDPs specified as credential providers.
- Apache with mod\_shib, configured to use a discovery service to dynamically resolve available IDPs in a federation.

In the second case the apache server (mod\_shib) will add some HTTP headers, namely REMOTE\_USER, EMAIL, etc, which the underlying application can use as login credentials.

If there is a plugin for Discourse that can handle the second case, I can easily configure an apache proxy in front of my docker for this purpose. I haven’t found a plugin like that. Anyone knows if one exists?