# Custom Authorization Plugins

**URL:** <https://discuss.elastic.co/t/custom-authorization-plugins/26173>\
**Category:** Kibana\
**Created:** [July 23, 2015, 4:06pm UTC](https://discuss.elastic.co/t/custom-authorization-plugins/26173 "2015-07-23T16:06:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcantrill](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jcantrill/32/26253_2.png) [@jcantrill](https://discuss.elastic.co/u/jcantrill)\
**Post date:** [July 23, 2015, 4:06pm UTC](https://discuss.elastic.co/t/custom-authorization-plugins/26173/1 "2015-07-23T16:06:47Z")

</div>

I'm currently working to integrate Kibana as part of our ELK stack for OpenShift and need to be able to pass a user's token to Kibana for it's subsequent use when making queries to ElastiSearch. Is there any functionality that would support this use case or could someone advise where to being in order to write the appropriate plugin?

---

<div class="post-metadata">

**Author:** ![tbragin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tbragin/32/45166_2.png) [@tbragin](https://discuss.elastic.co/u/tbragin)\
**Post date:** [July 24, 2015, 12:32am UTC](https://discuss.elastic.co/t/custom-authorization-plugins/26173/2 "2015-07-24T00:32:56Z")

</div>

Shield is going to add support for custom realms in a future release, which would allow you to support custom SSO frameworks.

---

<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:** [July 6, 2017, 2:15pm UTC](https://discuss.elastic.co/t/custom-authorization-plugins/26173/3 "2017-07-06T14:15:52Z")

</div>