You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/blog/integrating-hpe-greenlake-webhooks-with-splunk.md
+10-4Lines changed: 10 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -331,12 +331,18 @@ The complete integration flow works as follows:
331
331
> 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
332
332
333
333
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
+
334
340
3. Event processing flow
335
341
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.
0 commit comments