Track IP on validate controls whether validate requests participate in IP tracking and enforcement.
For the current live platform, this behavior is effectively always on.
Current live behavior
- Validate requests participate in IP checks
- Validate requests participate in IP tracking for products using IP controls
- You do not need to configure a separate validate-only IP mode right now
What this means in practice
When a customer validates a license, the request is treated as part of the normal IP rules for that product. That means KeyPort can:
- evaluate blacklist rules
- check whether the IP is already registered
- apply IP registration rules
- enforce
max_ips limits
Example
If a customer validates from a new machine:
- KeyPort evaluates that IP against the product’s active IP policy
- the request can be accepted, rejected, or registered depending on the product and license settings
Why this matters
This keeps validation behavior consistent. The same request that proves a license is valid also participates in the product’s IP enforcement path, instead of skipping it.
If you are troubleshooting IP behavior, always treat validate as part of the IP system for live products.
