From f5a853997f6dba0e01f76e28552f053a4713fa92 Mon Sep 17 00:00:00 2001
From: Rebecca Wheeler <rebecca.wheeler@wisc.edu>
Date: Thu, 13 Apr 2023 16:15:04 -0500
Subject: [PATCH] removed a CON that API team pointed out was false
---
docs/tutorials/PersonAPI/Webhooks.md | 2 --
1 file changed, 2 deletions(-)
diff --git a/docs/tutorials/PersonAPI/Webhooks.md b/docs/tutorials/PersonAPI/Webhooks.md
index 622b453..da38c86 100644
--- a/docs/tutorials/PersonAPI/Webhooks.md
+++ b/docs/tutorials/PersonAPI/Webhooks.md
@@ -123,8 +123,6 @@ After all of the Assets above have been created and tested we can create a “Pr
2. Configuring Process Objects can be time consuming
- This is especially true for Person API as the data structures can be dynamic.
3. Each process needs to be built from scratch
-4. IICS CAI does not have the ability to read headers at the start of the process. The Person API Webhook sends a token in the header that consumers can validate to make sure that the event data is coming from the correct source. This is not possible.
- - To facilitate this validation process, changes need to be made to the Person API. Example, send the token in the request body instead.
### Pros:
1. It is easy to create an endpoint that can be used as a webhook endpoint.
--
GitLab