The network license service authorizes and controls access to shared licenses on a network. Before you can use the network license service to license your software you will need to configure it to exclusively authorize licenses created by your company.
Agile.net Copy Protection uses license keys created using public-key cryptography, also known as asymmetric cryptography. Public-key cryptography requires two separate keys, one of which is secret (or private) and one of which is public. Although different, the two parts of this key pair are mathematically linked. The public key is used to verify a digital signature, whereas the private key is used to create a digital signature. The private key, is kept secret so that no other user can sign the data.
By creating a digital signature with the private key and associating it with the network license service we can ensure that a network license can only read and validate licenses created by a unique software publisher. If the signature has been modified since it was created by the authorized user validation will fail. By generating a network license using a distinct pair of keys we can be sure that licenses created with one key pair cannot be used to unlock software protected with a different set of keys.
To generate a network license service using a unique set of keys:
By default the network license service listens on port 8127, to modify this setting:
In production environments the Network License Service is installed as a windows service. To install it as a windows service:
To uninstall the Network License Service:
The network licensing service supports a logging system that allows administrators to actively watch network licensing activity. The network license service logs all activity locally to the Network License Service application folder. In case there is no write permission in that folder, logs are written to %LocalAppData%\SecureTeam\NetworkLicenseService.