Uploaded image for project: 'Commons'
  1. Commons
  2. COMMONS-339

Commons Secrets Integration in other Commons APIs

    Details

    • Type: Epic
    • Status: Closed
    • Priority: Blocker
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Secrets
    • Labels:
    • Epic Name:
      Commons Secrets Integration (Commons)
    • Target Version/s:
    • Epic Status:
      Done
    • Threat Model Attached:
      N/A

      Description

      APIs in commons that use or manipulate cryptographic secrets should use the new commons secrets API that has been added in order to do so. This should make integration into products simpler.

      Existing APIs that deal in raw (byte[], Key, etc.) secret values should be removed.

      Acceptance Criteria

      • All APIs that use cryptographic secrets should be switched to use the Secrets API
      • The only remaining APIs that use raw secret values are those for which integration is made difficult in products. Those APIs should be marked as deprecated.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jamesphillpotts James Phillpotts
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: