Changing License Server settings

Use the Configuration page in the License Server Console to modify server settings: 

•License Address. The license address is the address and port on which the license server listens for license requests from clients. The default is 0.0.0.0:1820 to access UDP traffic on port 1820 for all network interfaces. If the port value is changed, the clients must be configured to use the different port.

Example: 0.0.0.0:1820

•Force secure delivery of licenses. The Client must use HTTPS for traffic to and from the License Server. This option requires a Velocity Client version 2.1.23 or newer. The License Server does not accept license requests over UDP. The Client must be configured with the License Server address.

•HTTP Address. The HTTP address is the address and port of the License Server for the web browser. The default is 0.0.0.0:4420, which would mean a web browser address of http://[your computer name]:4420/. You should either change the HTTP address to localhost (the loopback address) so the browser would need to be running on the same computer as License Server to access it, or make sure you specify an HTTP filter and/or username and password to restrict access.

Example: localhost:4420

•Username and Password. The username and password can be used to restrict access to the License Server Console. Both must be specified for the access to be restricted. You must set a username and password in order to synchronize information between servers.

•HTTP Filter. Limits the IP addresses that are allowed to access the License Server Console. You can have multiple entries; access will be allowed if any of the entries match. If no values are configured, access is allowed from any IP address. Use CIDR notation to represent an entire subnet.

Example: 127.0.0.0/8 (This will allow access from 127.0.0.0 to 127.255.255.255)

Example: 10.20.0.0/14 (This will allow access from 10.20.0.0 to 10.23.255.255)

Example: 192.168.3.87 (This will allow access only from 192.168.3.87)

•Other Servers. Specify the IP address and port, username, and password for another license server. The current server uses a secure connection to synchronize its license information with the servers in the list. The first time the server connects, it displays the certificate information for the remote server. If the server has a self-signed certificate, you should make sure the certificate details displayed for the remote server are correct before proceeding. If the details do not match, it may be an indicator of a man-in-the-middle attack. For information on viewing the certificate details in Windows, see View Certificates with the Certificate Manager tool.

License servers that use this feature should have a static IP address. The port used should match the License Address port. When you are adding an Other Server, provide the IP address and port in the Address field using the following format: 

[IP address]:[port]

IPv6 is not supported.

When you add a license server to the Other servers list, each server sends all of its license information as well as its current list of Other servers. Subsequent sync messages contain only the changed information and are triggered by the following actions: adding, modifying, or deleting a license; adding or deleting a device; reassigning a license to a device; or receiving a new sync message from another license server. (If a license server receives a sync message with data it already has, that does not trigger another sync message.)

You should use the Other servers list in situations where there is a reliable network connection between the license servers. If a license server gets out of sync, restarting the license server triggers a full synchronization.

When you remove a server from the list, the current server attempts to contact the remote server and disable any further sync messages. Information that has already been synchronized is not removed from either server. If the remote server cannot be reached, the server remains in the list.

The Other Servers feature in 5.1 uses the server certificates to establish a secure connection. Servers that are older than 5.1 or do not have a certificate do not support this secure connection and are unable to sync.

•Site ID. Use Site IDs to ensure that licenses go to the correct devices. When you add a license to the License Server and associate a Site ID with it, only Clients that have the same Site ID can use the licenses. If you plan to use Site IDs, create the Site IDs before you add the licenses to the server.

Site IDs are optional. Licenses are not required to have a Site ID associated with them. However, if a Client has a Site ID configured, it can only use a license that has the same Site ID.

•Server Site ID. The site ID for this license server. A value of ʺ0ʺ should be used if you are not using the Site ID feature or if the License Server will be supporting multiple sites.

•Site ID For Unassigned Devices. Determines which Site ID to use for Clients that do not report a Site ID. This includes devices that donʹt have a Site ID configured, and older clients that do not support the configuration of site IDs. Leave this field blank if you are not using Site IDs.

•Show All Licenses. Displays all licenses on the Licenses page. If you disable this option, only the licenses with a Site ID of 0 or a Site ID matching the Server Site ID are displayed.

•Reassign after __ Days. Sets the number of days a license goes unused before it is allowed to be redistributed to a different device. This is useful if, for example, you get a replacement device and want the replacement device to be able to access the previous deviceʹs license. Valid values are 5 ‐ 365 days, with the default being 14 days. A value of 0 can also be used if you never want unused licenses to be redistributed.

•Logging Settings. Refer to Updating logging levels for details about these settings.

To change the settings:

1.In the License Server Console, click the Configuration menu item.

2.On the Configuration page, modify the options as desired. When you are finished, click Save and Apply to update the settings.

If you change the HTTP address, you must restart the License Server for the changes to take effect. For information on restarting the License Server, see Installing the License Server.