# Session management for restconf

**URL:** <https://dmap-community.ductus.global/t/session-management-for-restconf/1312>\
**Category:** Other Northbound Interfaces\
**Created:** [June 8, 2017, 5:56am UTC](https://dmap-community.ductus.global/t/session-management-for-restconf/1312 "2017-06-08T05:56:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Decode](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@Decode](https://dmap-community.ductus.global/u/Decode)\
**Post date:** [June 8, 2017, 5:56am UTC](https://dmap-community.ductus.global/t/session-management-for-restconf/1312/1 "2017-06-08T05:56:02Z")

</div>

Is their support for maintaining session in confd for restconf.  
Some sort of token based mechanism

Can we integrate other implementation for that?  
Suggestions please

---

<div class="post-metadata">

**Author:** ![jlawitzke](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/jlawitzke/32/54_2.png) [@jlawitzke](https://dmap-community.ductus.global/u/jlawitzke)\
**Post date:** [June 8, 2017, 1:18pm UTC](https://dmap-community.ductus.global/t/session-management-for-restconf/1312/2 "2017-06-08T13:18:04Z")

</div>

By definition, REST is stateless. Therefore, the RESTCONF RFC does not define such a mechanism.

---

<div class="post-metadata">

**Author:** ![Decode](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@Decode](https://dmap-community.ductus.global/u/Decode)\
**Post date:** [June 9, 2017, 5:23am UTC](https://dmap-community.ductus.global/t/session-management-for-restconf/1312/3 "2017-06-09T05:23:44Z")

</div>

Do we have to send authentication parameters in every request.  
This is definitely not the best way? It’s an extra overhead.

What I have goofed around is that we can use token based session management (like oAuth protocol). Can that be handled in confd or we have to take care of that separately.

Is there any enhancement planned for session handling in confd?  
Currently we are on version 6.2.1