Skip to content

Commit 1c5ae5b

Browse files
committed
Update Blog “integrating-hpe-greenlake-webhooks-with-splunk”
1 parent f1d40d7 commit 1c5ae5b

File tree

1 file changed

+10
-4
lines changed

1 file changed

+10
-4
lines changed

content/blog/integrating-hpe-greenlake-webhooks-with-splunk.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -331,12 +331,18 @@ The complete integration flow works as follows:
331331
> Note: See [this blog](https://developer.hpe.com/blog/getting-started-with-the-hpe-greenlake-cloud-eventing-framework/) to learn how to register a new webhook handler in HPE GreenLake
332332
333333
2. Webhook handler verification process
334+
335+
* HPE GreenLake sends a verification challenge to your custom endpoint.
336+
* The custom REST handler receives the challenge and validates it using HMAC SHA-256.
337+
* The handler responds with the computed verification hash.
338+
* HPE GreenLake confirms the webhook and marks it as active.
339+
334340
3. Event processing flow
335341
336-
* HPE GreenLake sends event data to the custom handler endpoint.
337-
* The custom REST handler validates the HMAC signature.
338-
* The handler forwards validated events to HEC.
339-
* Splunk HEC ingests the data for analysis and visualization.
342+
* HPE GreenLake sends event data to the custom handler endpoint.
343+
* The custom REST handler validates the HMAC signature.
344+
* The handler forwards validated events to HEC.
345+
* Splunk HEC ingests the data for analysis and visualization.
340346
341347
4. Data flow diagram
342348

0 commit comments

Comments
 (0)