# No handler found for uri \[/api/security/v1/login\] for auto-authentication embedded iframe

**URL:** https://discuss.elastic.co/t/no-handler-found-for-uri-api-security-v1-login-for-auto-authentication-embedded-iframe/102627
**Category:** Kibana
**Created:** [October 3, 2017, 10:32pm UTC](https://discuss.elastic.co/t/no-handler-found-for-uri-api-security-v1-login-for-auto-authentication-embedded-iframe/102627 "2017-10-03T22:32:48Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![nomAAd](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nomaad/32/22738_2.png) [@nomAAd](https://discuss.elastic.co/u/nomAAd)
#### Post date: [October 3, 2017, 10:32pm UTC](https://discuss.elastic.co/t/no-handler-found-for-uri-api-security-v1-login-for-auto-authentication-embedded-iframe/102627/1 "2017-10-03T22:32:48Z")

</div>

Hi,  
I've made an MVC web app which has embedded iframes of Kibana Dashboards we have created using Version 5.5.2. We do have an initial login, so we don't want our users to enter their credentials twice. I've read through previous threads POSTING to:

`/api/security/v1/login`  
`{`  
`"password":"<password>",`  
`"username":"<username>"`  
`}`

with an appropriate additional header `kbn-version:5.5.2` to retrieve/set a cookie however I get a 400 Bad Request with the message `No handler found for uri [/api/security/v1/login] and method [POST]`.  
Our Kibana instance is hosted on [elastic.co](http://elastic.co). From my understanding that if that POST is successful the server should respond with a cookie header where then you can set within your current session.  
Please let me know if my logic is wrong or I am missing any steps. Some guidance will be greatly appreciated!  
Thanks

Link to previous thread: [https://discuss.elastic.co/t/authenticating-to-iframe-embedded-kibana-dashboard/71129/5](https://discuss.elastic.co/t/authenticating-to-iframe-embedded-kibana-dashboard/71129/5)

---

<div class="post-metadata">

### Author: ![lukas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas/32/6812_2.png) [@lukas](https://discuss.elastic.co/u/lukas)
#### Post date: [October 4, 2017, 3:53pm UTC](https://discuss.elastic.co/t/no-handler-found-for-uri-api-security-v1-login-for-auto-authentication-embedded-iframe/102627/2 "2017-10-04T15:53:44Z")

</div>

Are you making sure to add your base path before `/api/security/v1/login`?

---

<div class="post-metadata">

### Author: ![nomAAd](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nomaad/32/22738_2.png) [@nomAAd](https://discuss.elastic.co/u/nomAAd)
#### Post date: [October 4, 2017, 9:08pm UTC](https://discuss.elastic.co/t/no-handler-found-for-uri-api-security-v1-login-for-auto-authentication-embedded-iframe/102627/3 "2017-10-04T21:08:01Z")

</div>

Hi,  
Pretty embarrassed by this but I've had my base path set to an old cluster that we deactivated. `/api/security/v1/login` works. Thanks for your help!

---

<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: [November 1, 2017, 9:08pm UTC](https://discuss.elastic.co/t/no-handler-found-for-uri-api-security-v1-login-for-auto-authentication-embedded-iframe/102627/4 "2017-11-01T21:08:13Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.