JavaScript must be enabled in order for you to use Knowledgebase Manager Pro. However, it seems JavaScript is either disabled or not supported by your browser. To use Knowledgebase Manager Pro, enable JavaScript by changing your browser options, then try again.
Learn more.

Licensing Authentication

Reference Number: AA-00639Views: 6525

0 Rating/ Voters

Deprecated: Licensing Authentication

As of the summer of 2016, the Legacy LumenVox Subscription Licensing system was replaced with the significantly improved Flexible Licensing model. All users of the legacy subscription system were contacted and migrated over to the new system prior to its decommission.

This documentation will be deleted in due course, but will remain available for informational purposes until then. All of the content on this page is no longer valid. Please refer to the Flexible Licensing documentation instead.

The LumenVox License Server (and associated license client) can be configured to run in an authentication mode. By default, authentication mode is disabled.

When the License Server is in authentication mode, it will only provide licenses to clients that provide a username and password. To enable authentication, you must create a license_authentication.conf file in which you specify a list of usernames and passwords, along with a type and quantity of licenses to which that user is entitled.

There is a corresponding setting in the client configuration file that simply takes a username and password. This is the username and password that any speech applications using the client files on that machine will supply. If you do not specify the AUTHENTICATION_USERNAME and AUTHENTICATION_PASSWORD values in the [AUTHENTICATION] section of the client_property.conf file, the client will not use authentication.

For more information on configuring your Speech Client for authentication, click here.

If either the client or the server is in authentication mode, they will not be able to communicate with other servers or clients that are not in authentication mode, so it is important to ensure you have all the machines in a given cluster set to either use authentication or not.

As a quick summary, in order to enable authentication perform the following steps: