# XPACK Custom Realm with SSO integration

**URL:** <https://discuss.elastic.co/t/xpack-custom-realm-with-sso-integration/108185>\
**Category:** Elasticsearch\
**Created:** [November 17, 2017, 6:53pm UTC](https://discuss.elastic.co/t/xpack-custom-realm-with-sso-integration/108185 "2017-11-17T18:53:59Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [November 24, 2017, 12:26pm UTC](https://discuss.elastic.co/t/xpack-custom-realm-with-sso-integration/108185/2 "2017-11-24T12:26:55Z")

</div>

Hi @jvemugunta,

At the moment Kibana X-Pack Security only recognizes `Authorization: Basic xxxx` as valid credentials even though Elasticsearch may support other authentication schemas.

The only option I can think of right now is to disable security in Kibana like described here: [Disable login in Kibana 5.3](https://discuss.elastic.co/t/disable-login-in-kibana-5-3/82998) or [Login in Kibana using Custom Realm installed in Elasticsearch](https://discuss.elastic.co/t/native-authentication-showing-up-even-if-it-is-disabled/91446). This way security will still be enforced by your realm at Elasticsearch, but you won't see Login screen in Kibana.

P.S. We're actively working on improving that situation in Kibana, stay tuned!

Let me know if you still have questions.

Thanks,  
Oleg

---

_[View the full topic](https://discuss.elastic.co/t/xpack-custom-realm-with-sso-integration/108185)._