Update Blog “integrating-hpe-greenlake-webhooks-with-splunk”

Author: Didier-Lalli

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

@@ -107,6 +107,26 @@ You can install and configure the endpoint handler directly on your Splunk Enter
 
 [Splunk Cloud has extra security controls](https://docs.splunk.com/Documentation/SplunkCloud/latest/RESTTUT/RESTandCloud), so you might need to take additional steps to allow your helper to communicate with the Splunk REST API.
 
+## Generate an Splunk REST API key 
+
+In order to use the custom REST endpoint in Splunk, you need to get an API key which HPE GreenLake will use to authenticate against Splunk when initially setting up the webhook and sending events. You can use the following cURL command to generate a key.
+
+```shell
+curl -k https://your-splunk-instance:8089/services/auth/login \
+     --data-urlencode username=YOUR_USERNAME \
+     --data-urlencode 'password=YOUR_PASSWORD’
+```
+
+The response will be:
+
+```
+<response>
+  <sessionKey>YOUR_SESSION_KEY</sessionKey>
+  <messages>
+    <msg code=""></msg>
+  </messages>
+</response>
+```
 ## Sample Python handler
 
 Let's create a custom REST endpoint handler in Python to handle the HPE GreenLake webhook validation and forwards events to Splunk HEC, once validated.
@@ -291,31 +311,6 @@ This allows you to get your HEC endpoint, which is used in the Python handler to
 
 `<https://<splunk-host>>:8088/services/collector/event`
 
- Don’t forget to modify the Python handler (shown above) line 7 accordingly.
-
-### Generate an Splunk REST API key 
-
-In order to use the custom REST endpoint in Splunk, you need to get an API key which HPE GreenLake will use to authenticate against Splunk when setiing up the webhook and sending events. You can use the following cURL command to generate a key.
-
-```shell
-curl -k https://your-splunk-instance:8089/services/auth/login \
-     --data-urlencode username=YOUR_USERNAME \
-     --data-urlencode 'password=YOUR_PASSWORD’
-```
-
-The response will be:
-
-```
-<response>
-  <sessionKey>YOUR_SESSION_KEY</sessionKey>
-  <messages>
-    <msg code=""></msg>
-  </messages>
-</response>
-```
-
- 
-
 ## Final integration flow
 
 The complete integration flow works as follows: