Subscribe to our monthly newsletter
As technology has evolved and virtual environments such as NFV and Cloud-Native have emerged, its slowly becoming less common for instrumentation applications to communicate with ConfD over trusted networks within physical network equipment. Network element management today requires that ConfD applications communicate over untrusted networks and it is becoming more and more common.
Our latest application note "Secure ConfD Client Application Communication" discusses mechanisms to make the ConfD client application IPC connection secure and shares an example on how to setup stunnel to authenticate and encrypt data between the ConfD daemon and ConfD client applications.
Helping clients seamlessly merge fixed and mobile networks for mobile operators is priority number one for Tessares. Yet, behind the scenes, they required stronger management and configuration capabilities. They needed a specific feature set that integrated with NETCONF and YANG and also supported SNMP. The choice was easy, Tail-f ConfD fit the bill supporting the required features.
We are less than a month away from MPLS + SDN + NFV World Congress. We will be at this year’s event in booth #207 discussing and demonstrating use cases for ConfD and how to use it to achieve better programmability.
If attending we would love to see you. To schedule a conversation email us at: email@example.com
While ConfD does provide a basic authentication mechanism which ConfD applications can use when making API calls via Inter-Process Communication (IPC) to the ConfD daemon, there is becoming a need to both authenticate and encrypt the IPC.