# Logging into Kibana from a React page using /api/security/v1/login

**URL:** https://discuss.elastic.co/t/logging-into-kibana-from-a-react-page-using-api-security-v1-login/95018
**Category:** Kibana
**Created:** [July 28, 2017, 10:09pm UTC](https://discuss.elastic.co/t/logging-into-kibana-from-a-react-page-using-api-security-v1-login/95018 "2017-07-28T22:09:24Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![weltenwort](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weltenwort/32/53885_2.png) [@weltenwort](https://discuss.elastic.co/u/weltenwort)
#### Post date: [July 31, 2017, 2:02pm UTC](https://discuss.elastic.co/t/logging-into-kibana-from-a-react-page-using-api-security-v1-login/95018/2 "2017-07-31T14:02:47Z")

</div>

Hi @Sannj,

that is definitely a problematic area of Kibana in combination with X-Pack. Usually we recommend one of two approaches:

- Use a reverse proxy for accessing the dashboards that injects an `Authorization` header.
- Use an ajax request before loading the iframes, which calls the API with the `Authorization` header to have the cookie set in the browser session.

From your description it sounds like you already tried the second approach. Could you elaborate what you mean by "the browser is not able to use it"?

---

_[View the full topic](https://discuss.elastic.co/t/logging-into-kibana-from-a-react-page-using-api-security-v1-login/95018)._