# Custom Security Extension and Realm Work for Kibana Login

**URL:** <https://discuss.elastic.co/t/custom-security-extension-and-realm-work-for-kibana-login/216116>\
**Category:** Kibana\
**Created:** [January 22, 2020, 6:15pm UTC](https://discuss.elastic.co/t/custom-security-extension-and-realm-work-for-kibana-login/216116 "2020-01-22T18:15:46Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![virgilp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/virgilp/32/49291_2.png) [@virgilp](https://discuss.elastic.co/u/virgilp)\
**Post date:** [February 11, 2020, 3:24pm UTC](https://discuss.elastic.co/t/custom-security-extension-and-realm-work-for-kibana-login/216116/3 "2020-02-11T15:24:37Z")

</div>

That doesn't work for login, which is in practice what you need for Kibana (API calls are far less infrequent than Elasticsearch). The token authentication provider performs login using user/pass credentials.  
I do not believe this to be possible right now (\*) - see also [Authentication provider in Kibana](https://discuss.elastic.co/t/authentication-provider-in-kibana/218725)

(\*) At least, not easily. One can do it with legacy plugins if xpack security is disabled; It may also be possibly by a mix of legacy & new platform code, but I don't believe it can be done in a new-platform plugin. Please do let me know if I'm wrong about that.

---

_[View the full topic](https://discuss.elastic.co/t/custom-security-extension-and-realm-work-for-kibana-login/216116)._