Adr for public and private keys (#583)

* Pushing draft adr for public and private keys

* Updating key names

* Updating ADR file

.pre-commit-config.yaml

@@ -9,7 +9,7 @@ repos:
       - id: check-symlinks
       - id: check-yaml
       - id: detect-private-key
-        exclude: (mock_credentials|.+\/JjwtEngine.java|.+\/resources\/(organization-report-stream-public-key.pem|trusted-intermediary-private-key-local.pem))
+        exclude: (mock_credentials|.+\/JjwtEngine.java|.+\/resources\/(organization-report-stream-public-key-local.pem|trusted-intermediary-private-key-local.pem))
       - id: end-of-file-fixer
       - id: no-commit-to-branch
       - id: trailing-whitespace

adr/014-keys.md

@@ -0,0 +1,33 @@
+# 14. Keys
+
+Date: 2023-10-23
+
+## Decision
+
+### Internal Keys
+
+These keys are used for the intermediary's internal use.  These keys will follow the following naming paradigm...
+
+`trusted-intermediary-<key type>-key-<environment>`.
+
+For example, `trusted-intermediary-private-key-staging` or `trusted-intermediary-public-key-prod`.
+
+### Organization Keys
+
+These are keys for external orgs to authenticate with us. Currently, report stream is the only organization we have. The pattern for the name of these keys is
+
+`organization-<org name>-<key type>-key-<environment>`.
+
+For example, `organization-report-stream-public-key-staging`
+
+## Status
+
+Accepted.
+
+## Context
+
+This naming convention applies to all locations where our keys are stored.  Previously, we didn't have a consistent naming convention across all our locations which caused confusion on which key was to be used in which context and environment.
+
+### Related Issues
+
+- #584