# Authentication in Kibana **URL:** https://discuss.elastic.co/t/authentication-in-kibana/173955 **Category:** Kibana **Created:** [March 26, 2019, 3:12pm UTC](https://discuss.elastic.co/t/authentication-in-kibana/173955 "2019-03-26T15:12:51Z") **Posts on this page:** 1 **Showing post:** 3
### Author: ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel) #### Post date: [March 26, 2019, 6:25pm UTC](https://discuss.elastic.co/t/authentication-in-kibana/173955/3 "2019-03-26T18:25:34Z")
Hey @Francisca_Lima, Kibana's CORS policy will prevent you from posting the user's credentials to the login endpoint. The best option is to do SSO using SAML. The ES docs for getting started using SAML are really good: [https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-saml-realm.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-saml-realm.html) The other option, which has it's limitations, is to use a reverse-proxy like NGINX to hard-code the credentials that are passed to Elasticsearch. This isn't great because anyone who can access the reverse proxy can automatically get access to Kibana, so it's really only good for providing the equivalent of "anonymous access". There is one other option at the moment, and that's to use something like an OAuth2 proxy to do impersonation: [https://www.elastic.co/blog/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) We're working on additional auth providers for ES/Kibana, so if none of this satisfies your needs, please let me know and I can direct you towards our feature requests which helps us prioritize the addition of these providers. --- _[View the full topic](https://discuss.elastic.co/t/authentication-in-kibana/173955)._