Licensing Operations¶
The VNetArmor Portal issues signed licences containing edition, entitlement, validity and capability information. Core and Managerd licensing behaviour depends on the installed runtime version. Verify the effective licence status and supported enforcement behaviour against that release; Portal entitlement alone does not prove runtime enforcement.
Operational expectations¶
- Activation uses a customer-specific activation token.
- Runtime heartbeat keeps license state current.
- Revoked or expired licenses should be detected.
- Capability and module limits should be reflected in the running service.
- Startup should warn when a newer entitled Core version is available, where configured.
Important environment variable¶
VNETARMOR_ACTIVATION_TOKEN=<customer activation token>
Do not place real tokens in public documentation, screenshots, or support tickets.
Troubleshooting¶
| Symptom | Likely cause | Resolution |
|---|---|---|
| License validation failed | Portal unreachable or token invalid. | Check portal URL, DNS, firewall, token, and time sync. |
| Capability not enabled | Edition does not include module or license not refreshed. | Refresh license and verify entitlement. |
| Heartbeat failures | Network or portal service issue. | Check logs and portal reachability from Core. |
GEO Capability and Third-Party Data¶
A VNetArmor edition may allow GEO filtering capability, but country lookup still requires a compatible GEO data source. The GEO database license is independent of the VNetArmor activation token and entitlement state.
During support reviews, operators should verify both:
- The VNetArmor license or edition enables GEO capability where required.
- The customer has installed and maintained a valid GEO database or approved trusted GEO metadata source.
Do not place third-party GEO database license keys, download credentials, or account identifiers in support tickets or public documentation.
Edition and entitlement reference¶
See Editions and Licensing for the public edition matrix, licence duration, resource limits, allocation policy and artifact compatibility.
Community has a non-expiring licence term, but remains subject to licence status and activation requirements. Lab is a separate time-limited evaluation edition. Commercial renewals and software upgrades are not equivalent to edition conversion.