# Authentication in transport layer

**URL:** <https://discuss.elastic.co/t/authentication-in-transport-layer/8629>\
**Category:** Elasticsearch\
**Created:** [August 3, 2012, 2:02pm UTC](https://discuss.elastic.co/t/authentication-in-transport-layer/8629 "2012-08-03T14:02:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jaguar](https://avatars.discourse-cdn.com/v4/letter/j/4af34b/32.png) [@Jaguar](https://discuss.elastic.co/u/Jaguar)\
**Post date:** [August 3, 2012, 2:02pm UTC](https://discuss.elastic.co/t/authentication-in-transport-layer/8629/1 "2012-08-03T14:02:19Z")

</div>

Hi,  
We are adding node-to-node authentication in ES. The authentication protocol requires a regular TCP connection, and need several rounds of message exchange. After that, the particular TCP connection could be regarded as secure for further ES node-to-node communication.  
I'm trying to implement this as a transport plugin, and would like to get some thought on how to utilize existing netty-transport.  
Idealy, there could be many different authentication protocols. Looks like it would be great if netty-transport allows "inject" authentication hook on per-connection basis.

Thanks!  
Jaguar

---

<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:** [July 6, 2017, 3:17am UTC](https://discuss.elastic.co/t/authentication-in-transport-layer/8629/2 "2017-07-06T03:17:49Z")

</div>

Closed on July 6, 2017, 3:17am UTC