Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-6075

[SaaS-STG] Important credential/keys should be stable after database obfuscation

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • None
    • SaaS
    • System
    • None

      Secrets shared between Backend, System, Zync, APIcast needs to be different from production. Due to obfuscation, they are changed every week. We need a stable way of generating those keys, otherwise end to end testing would fail every week.

       

      Procedure:

      • Those keys are stored in Vault
      • Restore the database
      • Update the database and reset the keys to the value stored in Vault

       

      Affected components 

      • APIcast cloud hosted is using a System APIcast mapping-service access token
      • Same for Backend shared key
      • Same for Zync Authentication Token

            Unassigned Unassigned
            hramihaj Hery Ramihajamalala (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: