I do not know what how the Java version of your RESTCONF client has anything to do with NSO. However, if you are running NSO 5.2 on Java 6, that is not supported. The current requirement is for Java 8 or higher.
Moreover, I would recommend you to move away from Java 6 as it is officially not supported by Oracle since Dec. 2018.
Answering to myself, maybe your error message is not NSO error but in your client? If that is the case, it may well be that Java 6 SSL implementation does not match RESTCONF requirements. One option that I think about is to user RESTCONF over HTTP (no TLS which is not recommended but possible in NSO) or to play with the ncs.conf file to find a TLS/SSL version or algorithms that would work.
It is best practice to avoid storing your secrets (e.g., passwords and shared keys) in plain text, either on NSO or on the device. In NSO, we support multiple encrypted data types that are encrypted using a local key. Similarly, many devices such as Cisco...
Cisco Developer Days, September 14-15, 2021
On Tuesday next week, we will open the doors to the 11th Cisco Developer Days!
If you have not registered for the free, virtual event, do it now!
What can you expect?
We have a packed 2-day agen...
In the blog post series called "Unlocking Performance in your NSO System" we talked about the need to measure performance and to profile the performance in order to identify bottlenecks. We didn't go into any details about how to do this. Last year at the...
Finally, as you may have seen in the News & Announcement, we have opened the landing page for the next Developer Days event in September! The September 14/15 event is the first in a series of three virtual events in the three regions (EMEAR/US/Asia Pa...
We are excited to announce that our call for speakers for our upcoming Developer Days events is open!
Automation is a journey in itself and no two journeys are alike. Planning and preparation are a must for any major project. Having an open mind to u...