Uploaded image for project: 'Managed Service - Streams'
  1. Managed Service - Streams
  2. MGDSTRM-8026

Use Master Secret in Admin and Canary

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • kasFleetShard-0.24.0
    • None
    • None
    • None
    • False
    • None
    • False
    • No
    • MGDSRVS-72 - Address identified security threats of the platform
    • MK - Sprint 217, MK - Sprint 218, MK - Sprint 220, MK - Sprint 221

      WHAT

      MGDSTRM-8024 creates the master secret from MK-CR. This secret needs to be used elsewhere sensitive information is currently read directly.

      WHY

      Once the master secret is created the inline sensitive information is removed. 

      HOW

      Admin server and Canary currently read this information, they need to change it such that sensitive info is read directly from the master secret.

      DONE

      All the components are reading the sensitive information from the master secret.

      Guidelines

      The following steps should be adhered to:

      • Required tests should be put in place - unit, integration, manual test cases (if necessary)
      • CI and all relevant tests passing
      • Changes have been verified by one additional reviewer against:
      • each required environment
      • each supported upgrade path
      • If the changes could have an impact on the clients (either UI or CLI), a JIRA should be created for making the required changes on the client side and acknowledged by one of the client side team members. PR has been merged
         

              srbiswas@redhat.com Srijoni Biswas
              rhn-engineering-rareddy Ramesh Reddy
              Kafka Fleet Services
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: