Sonatype Nexus Webhooks
To integrate Sonatype Nexus webhooks with ngrok:
This guide covers how to use ngrok to integrate your localhost app with Sonatype Nexus by using Webhooks. Sonatype Nexus webhooks can be used to notify an external application whenever specific events occur in your Sonatype Nexus account.
By integrating ngrok with Sonatype Nexus, you can:
- Develop and test Sonatype Nexus webhooks locally, eliminating the time in deploying your development code to a public environment and setting it up in 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 and without spending time reproducing events manually in your Sonatype Nexus account.
- Secure your app with Sonatype Nexus validation provided by ngrok. Invalid requests are blocked by ngrok before reaching your app.
Step 1: Start your app
For this tutorial, we'll use the sample NodeJS app available on GitHub.
To install this sample, run the following commands in a terminal:
Loading…
This will get the project installed locally.
Now you can launch the app by running the following command:
Loading…
The app runs by default on port 3000.
You can validate that the app is up and running by visiting http://localhost:3000. The application logs request headers and body in the terminal and responds with a message in the browser.
Step 2: Launch ngrok
Once your app is running successfully on localhost, let's get it on the internet securely using ngrok!
-
If you're not an ngrok user yet, just sign up for ngrok for free.
-
Go to the ngrok dashboard and copy your Authtoken.
Tip: The ngrok agent uses the auth token to log into your account when you start a tunnel. -
Start ngrok by running the following command:
Loading…
-
ngrok will display a URL where your localhost application is exposed to the internet (copy this URL for use with Sonatype Nexus).
Step 3: Integrate Sonatype Nexus
To register a webhook on your Sonatype Nexus repository follow the instructions below:
-
Access your Sonatype Nexus Repository Manager user interface and sign in using your administration account. Tip: The user interface URL depends on where you deployed your repository manager.
-
On the left menu, click System, click Capabilities, and then click Create capability on the Capabilities page.
-
On the Select Capability Type click either Webhook: Global or Webhook: Repository depending on which type of event you associate with your webhook. In this example, click Webhook: Global.
-
On the Create Webhook page, enter the URL provided by the ngrok agent to expose your application to the internet in the URL field (i.e.
https://1a2b-3c4d-5e6f-7g8h-9i0j.ngrok.app
). -
In the Available list, click repository and then click the greater-than button to move the repository value to the Selected list.
Run Webhooks with Sonatype Nexus and ngrok
Sonatype Nexus sends different request body contents depending on the event that is being triggered. You can trigger new calls from Sonatype Nexus to your application by following the instructions below.
-
On the Sonatype Nexus Repository Manager user interface, click Repository on the left menu and then click Repositories. In this example, click apt (hosted).
-
On the Repositories page, click Create Repository, click one of the Recipes from the list, enter any value in the Name, Distribution, and Signing Key, and then click Create repository.
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. Click on any request to view detailed information about both the request and response.
By default, accounts only collect traffic metadata to avoid exposing secrets. You must enable full capture in the Observability section of your account settings to capture complete request and response data.
Use the traffic inspector to:
- 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
-
Modify the request (optional): Edit any part of the original request, such as changing field values in the request body.
-
Send the request by clicking Replay.
Your local application will receive the replayed request and log the data to the terminal.
Secure webhook requests
The ngrok signature webhook verification feature allows ngrok to assert that requests from your Sonatype Nexus webhook are the only traffic allowed to make calls to your localhost app.
Note: This ngrok feature is limited to 500 validations per month on free ngrok accounts. For unlimited, upgrade to Pro or Enterprise.
This is a quick step to add extra protection to your application.
-
Access your Sonatype Nexus Repository Manager user interface and sign in using your administration account. Tip: Your Sonatype Nexus Repository Manager URL depends on where you deployed your repository manager.
-
On the left menu, click System, click Capabilities, and then click Webhook: Global or Webhook: Repository depending on which type of capability you created before.
-
On the Webhook page, click the Settings tab, and then enter
12345
in the Secret Key field. -
Create a file named
sonatype_nexus_policy.yml
, replacing{your webhook secret}
with the value of the Secret Key field:Loading…
-
Restart your ngrok agent by running the command:
Loading…
-
On the Sonatype Nexus Repository Manager user interface, click Repository on the left menu and then click Repositories. In this example, click apt (hosted).
-
On the Repositories page, click Create Repository, click one of the Recipes from the list, enter any value in the Name, Distribution, and Signing Key, and then click Create repository.
Confirm your localhost app receives an event notification and logs both headers and body in the terminal.
Verify that your local application receives the request and logs information to the terminal.