If you don’t see your preferred webhook provider, you can request support for it.
- Develop and test Sonatype Nexus webhooks locally without deploying to a public environment or setting up HTTPS.
- Inspect and troubleshoot requests from Sonatype Nexus in real time via the inspection UI and API.
- Modify and replay Sonatype Nexus webhook requests with a single click instead of reproducing events manually in your Sonatype Nexus account.
- Secure your app with Sonatype Nexus webhook validation provided by ngrok. Invalid requests are blocked by ngrok before reaching your app.
What you’ll need
- An ngrok account and your authtoken.
- The ngrok agent installed.
- Node.js installed (for the sample app, or use your own app).
- A Sonatype Nexus Repository Manager instance.
1. Start your app
For this tutorial, you can use the sample Node.js app on GitHub. To install the sample, run the following in a terminal:http://localhost:3000.
The app logs request headers and body in the terminal and shows a message in the browser.
2. Expose your app with ngrok
Once your app is running locally, you’re ready to put it online securely using ngrok.- Copy your ngrok authtoken from the dashboard.
-
Start ngrok:
- Copy the URL ngrok displays. Your app is now exposed at that URL for use with Sonatype Nexus.
3. Configure Sonatype Nexus to send webhooks
Follow Sonatype’s documentation for configuring a webhook capability, and set the following:- Capability type: choose Webhook: Global or Webhook: Repository (for this example, Webhook: Global).
- URL: your ngrok URL (for example,
https://1a2b-3c4d-5e6f-7g8h-9i0j.ngrok.app). - Events: select the event categories you want to receive (for this example, repository events).
- Secret Key: set a secret and note it for the verification step below.
Run webhooks with Sonatype Nexus and ngrok
Sonatype Nexus sends a different request body depending on the event. To trigger a call to your app, create a repository or perform another action that matches the events you selected. Confirm your localhost app receives an event notification and logs both headers and body in the terminal.Inspecting requests
ngrok’s Traffic Inspector captures all requests made through your ngrok endpoint to your localhost app. Select any request to view detailed information about both the request and response.To avoid exposing secrets, accounts only collect traffic metadata by default.
You must enable full capture in the Traffic Inspector section of your account settings to capture complete request and response data.
- Validate webhook payloads and response data
- Debug request headers, methods, and status codes
- Troubleshoot integration issues without adding logging to your app
Replaying requests
Test your webhook handling code without triggering new events from your service using the Traffic Inspector’s replay feature:- Send a test webhook from your service to generate traffic in your Traffic Inspector.
- Select the request you want to replay in the traffic inspector.
-
Choose your replay option:
- Click Replay to send the exact same request again
- Select Replay with modifications to edit the request before sending
- (Optional) Modify the request: Edit any part of the original request, such as changing field values in the request body.
- Send the request by clicking Replay.
Secure webhook requests
ngrok can verify that incoming requests are from your Sonatype Nexus webhook so only that traffic reaches your app.Webhook verification is limited to 500 validations per month on free accounts.
If you need more, you can upgrade to Hobbyist or Pay-as-you-go.
See TPU Pricing for details.
- In your Sonatype Nexus Repository Manager, go to System, Capabilities, and the webhook capability you created (Webhook: Global or Webhook: Repository).
-
On the Webhook page, open the Settings tab and enter a value in Secret Key (for example,
12345). -
Create a Traffic Policy file named
sonatype_nexus_policy.yml. Replace{your webhook secret}with the Secret Key value: -
Restart ngrok with the policy file:
- Trigger an event (for example, create a repository as above) to send a request.