# HTTP Authentication

**URL:** <https://discuss.dgraph.io/t/http-authentication/1971>\
**Category:** Users\
**Created:** [November 19, 2017, 5:31pm UTC](https://discuss.dgraph.io/t/http-authentication/1971 "2017-11-19T17:31:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![amir](https://avatars.discourse-cdn.com/v4/letter/a/c37758/32.png) [@amir](https://discuss.dgraph.io/u/amir)\
**Post date:** [November 19, 2017, 5:31pm UTC](https://discuss.dgraph.io/t/http-authentication/1971/1 "2017-11-19T17:31:01Z")

</div>

When will you have authentication for the HTTP Client?

Thanks

---

<div class="post-metadata">

**Author:** ![mrjn](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/mrjn/32/775_2.png) [@mrjn](https://discuss.dgraph.io/u/mrjn)\
**Post date:** [November 19, 2017, 11:46pm UTC](https://discuss.dgraph.io/t/http-authentication/1971/2 "2017-11-19T23:46:54Z")

</div>

We allow TLS connections. But currently, there’s no other way. If you need to authenticate a client (login), you should do it in a layer above Dgraph. Dgraph does provide a secure way to store passwords, which can help with that.

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex007/uploads/dgraph/original/2X/2/2b38fdece2abe5814f2e51bee69d1e67fc304b0a.png) [@system](https://discuss.dgraph.io/u/system)\
**Post date:** [December 19, 2017, 11:47pm UTC](https://discuss.dgraph.io/t/http-authentication/1971/3 "2017-12-19T23:47:08Z")

</div>

Closed on December 19, 2017, 11:47pm UTC

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