Uploaded image for project: 'Network Controller'
  1. Network Controller
  2. SDNC-556

Develop mechanism to configure keys and certificates for NETCONF/TLS in ODL

    XMLWordPrintable

Details

    • Epic
    • Status: Closed
    • High
    • Resolution: Done
    • None
    • Dublin Release
    • None
    • None
    • Develop mechanism to configure keys and certificates for NETCONF/TLS in ODL
    • To Do

    Description

      In order to use the ODL netconf-connector with TLS, keys and certificates must be installed. A mechanism to do this at run-time must be defined and implemented in the controller.

      As this is a security related feature, the proposed solution shall also be discussed in SECCOM.

      Note:

      • Two options have been investigated for NETCONF/TLS client certificate generation: 1) manually outside of ONAP 2) by AAF. For Dublin option (1) will be supported. Option (2) is a possible extension for future release.

      Attachments

        Issue Links

          blocks

          Sub-task - The sub-task of the issue CCSDK-1028 Send the apply configuration message and check if the node was configured as expected

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed
          is blocked by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SDNC-551 OpenDaylight Fluorine Support

          • Highest - Catastrophic defect that causes total failure of the software or unrecoverable data loss with no available workaround. Complete shut-down of the process, nothing can proceed further. Blocks testing of the product / feature. Must be fixed in the next build.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SDNC-555 Install ODL features for NETCONF by default

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed
          mentioned in

          Page Loading...

          Page Loading...

          # Subject Branch Project Status CR V
          79717,5 SDNC-660: Helm integration for Netconf over TLS master oom Status: MERGED +2 +1
          82055,6 CSIT for SDNC Netconf Configuration master integration/csit Status: MERGED +2 +1
          82918,3 SDNC-665: Python script for adding to ODL keystore master sdnc/oam Status: MERGED +2 +1
          82937,2 SDNC-665: Change to startODL for oam repo master oom Status: MERGED +2 +1
          83758,4 Certificate installation and mount tests Removed Duplicate files Change-Id: I69782b3bc426dac02c691392ae679aeedcf81ee3 Signed-off-by: Rahul Yadav <rahul4talk@gmail.com> Issue-ID: SDNC-660 master integration/csit Status: ABANDONED +1 -1
          83793,1 Added sdnc post deploy csit tests master ci-management Status: MERGED +2 +1
          83968,3 Removed casablanca branch verify parameter master ci-management Status: MERGED +2 +1

          Activity

            People

              gummar Raj Gumma
              eoskmal Oskar Malm
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: