From 89e23acde5e860460ffb67980732a0cb86c715fd Mon Sep 17 00:00:00 2001 From: Matt Bishop Date: Tue, 29 Oct 2024 09:53:57 -0400 Subject: [PATCH] Clarify 400 vs 403 --- docs/architecture/adr/0023-integration-identifiers.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/architecture/adr/0023-integration-identifiers.md b/docs/architecture/adr/0023-integration-identifiers.md index 46e27fde..ec4cc76e 100644 --- a/docs/architecture/adr/0023-integration-identifiers.md +++ b/docs/architecture/adr/0023-integration-identifiers.md @@ -74,8 +74,9 @@ form their provided client version specifically to accurately represent supporte client-server interactivity. Operations teams will perform the necessary development to validate that required headers are -present and enable its enforcement after that time; invalid requests will be rejected as a -`400 Bad Request`. +present and enable its enforcement after that time; requests will be rejected as a `400 Bad Request` +when required headers are missing and a `403 Forbidden` when provided headers or their values are +not supported. A process will be established for integrations to submit support tickets requesting a client identifier and secret. Customer Success will work with operations teams to register integrations and