Deployment: Invicti Platform on-demand, Invicti Platform on-premises
Package: Invicti API Security Standalone or Bundle
Reuse NTA importer
Reinstall the Network Traffic Analyzer (NTA) without losing its connection to Invicti Platform. This document explains what you can reuse, depending on whether you kept the Reconstructor persistent volume when you uninstalled the NTA.
Why this matters
If you pick the wrong option, the NTA can look healthy after the reinstall and then go offline days later, when its registration token expires. Knowing whether your persistent volume is still in place tells you which option works, so you avoid 401 Unauthorized errors and an NTA that stops sending data.
How NTA tokens work
- Registration token: Authenticates the NTA with Invicti Platform when it connects for the first time. A registration token expires after 3 days (72 hours) on Invicti Platform on-demand and after 24 hours on Invicti Platform on-premises.
- Usage token: The NTA receives it when it registers for the first time, and stores it on its persistent volume, which you configure with the
reconstructor.persistentVolume.nodeNameparameter. The usage token keeps the NTA connected after the registration token expires. On Invicti Platform on-demand, a usage token is valid for 90 days (2160 hours), and the NTA refreshes it automatically.
Use a separate registration token for each NTA deployment. Only the first NTA that uses a registration token receives a usage token. Another NTA that uses the same token connects, but stops when the registration token expires.
Choose how to reuse the importer
Your options depend on what happened to the persistent volume when you uninstalled the NTA.
| Your situation | What to do |
|---|---|
You kept the persistent volume. In Kubernetes, you didn't delete the Reconstructor PersistentVolume and PersistentVolumeClaim. In Docker Compose, you ran docker compose down without --volumes. | Reinstall with your existing registration token. The NTA reconnects, even after the registration token has expired. |
You removed the persistent volume. In Kubernetes, you deleted the PersistentVolume and PersistentVolumeClaim. In Docker Compose, you ran docker compose down --volumes. | Create a new NTA source and a new registration token. |
Reinstall with your existing registration token
If you kept the persistent volume, the volume still holds the usage token. Install the NTA again with the same registration token, credentials, and reconstructor.persistentVolume.nodeName value you used for the initial installation.
- Find the registration token you saved when you first generated it. Invicti Platform doesn't show the token again after you leave the page.
- Run the install or upgrade command for your integration:
Save your registration tokens securely when you first generate them (for example, in a password manager) so you can reuse them.
Set up a new NTA source after removing the volume
If you removed the persistent volume, the stored usage token is gone, and your existing registration token no longer gives the NTA a long-lived connection. Create a new NTA source with its own registration token:
- Create a new NTA source and generate its registration token. For the steps, refer to the Generate a new registration token document.
- Install the NTA with the new registration token. Include the
reconstructor.persistentVolume.nodeNameparameter so the Reconstructor can store its usage token. For the commands, see the install steps of your integration: - Wait until the new source shows as online.
- Select Discovery from the left-side menu. Under API configuration, select API sources, and delete the old NTA source. Already discovered APIs remain in your API Inventory.
You can generate a new registration token on the existing NTA source, and the NTA connects with it. However, the NTA doesn't receive a new usage token, so it stops sending data when that registration token expires. The source then shows Offline. Create a new source instead.
Troubleshooting
The NTA returns 401 Unauthorized after I reinstall it with my existing token
The registration token no longer works if it expired or if you removed the persistent volume. A registration token expires after 3 days (72 hours) on-demand and after 24 hours on-premises, and a removed volume takes the stored usage token with it. Create a new NTA source and install the NTA with its token, as described in Set up a new NTA source after removing the volume. Confirm that your command includes the reconstructor.persistentVolume.nodeName parameter.
The source shows Offline and the NTA logs 401 Unauthorized
The NTA can't authenticate. This happens when the NTA runs without a stored usage token and its registration token has expired, for example after you removed the persistent volume and reused the source with a new registration token. Create a new NTA source, as described in Set up a new NTA source after removing the volume.
The Reconstructor pod stays in Pending state after I reinstall the NTA
The persistent volume is tied to the node you set in reconstructor.persistentVolume.nodeName. Use the same node name as in your initial installation.
Need help?
Invicti Support team is ready to provide you with technical help. Go to Help Center