# Curl to Elasticsearch node when security is enabled

**URL:** <https://discuss.elastic.co/t/curl-to-elasticsearch-node-when-security-is-enabled/164871>\
**Category:** Elasticsearch\
**Created:** [January 19, 2019, 1:19am UTC](https://discuss.elastic.co/t/curl-to-elasticsearch-node-when-security-is-enabled/164871 "2019-01-19T01:19:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![li\_jessen2016](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/li_jessen2016/32/38817_2.png) [@li\_jessen2016](https://discuss.elastic.co/u/li_jessen2016)\
**Post date:** [January 19, 2019, 1:19am UTC](https://discuss.elastic.co/t/curl-to-elasticsearch-node-when-security-is-enabled/164871/1 "2019-01-19T01:19:50Z")

</div>

When I enables security in Elasticsearch, I can't visit it using just curl "hostname:9200/" unless I add curl -u username:password. And I just used built-in users of elastic.  
Is this what security feature means by requiring authentication?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 19, 2019, 1:21am UTC](https://discuss.elastic.co/t/curl-to-elasticsearch-node-when-security-is-enabled/164871/2 "2019-01-19T01:21:35Z")

</div>

That is one aspect, yes.

---

<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:** [February 16, 2019, 1:21am UTC](https://discuss.elastic.co/t/curl-to-elasticsearch-node-when-security-is-enabled/164871/3 "2019-02-16T01:21:36Z")

</div>

Closed on February 16, 2019, 1:21am UTC

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