Uploaded image for project: 'Data Collection, Analytics, and Events'
  1. Data Collection, Analytics, and Events
  2. DCAEGEN2-592

Data encryption via TLS (components impact)

    XMLWordPrintable

Details

    • Story
    • Status: Closed
    • Medium
    • Resolution: Done
    • Dublin Release
    • El Alto Release
    • None
    • None

    Description

      Ensure each components can support encryptions (via https) for its interfaces For R3 all DCAE components require to data flow and control flow to be encrypted. 

      Component that presents an API (DH, CBS, InventoryAPI, VESCollector, HV-VES) must present it via HTTPS, authenticating itself with its server cert (cert will be made available part of DCAE deployment setup) 

      2-way Mutual SSL (which require that API clients present a TLS certificate) should be enabled via configuration (based on CADI client availability)

      Support for RBAC via configuration (to allow integration with AAF later). Actual RBAC integration through AAF is tracked under DCAEGEN2-597

       

       

      Attachments

        Issue Links

          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DCAEGEN2-780 Data encryption via TLS - deployment-handler

          • 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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DCAEGEN2-781 Data encryption via TLS - policy-handler

          • 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

          Bug - A problem which impairs or prevents the functions of the product. DCAEGEN2-851 use https when policy-handler talks to deployment-handler

          • 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
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              vv770d Vijay Venkatesh Kumar
              vv770d Vijay Venkatesh Kumar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: