Getting Started with License Filebased. FLEXnet Publisher Licensing Toolkit 11.5 P/N: FNP-115-GSLF01

Transcription

1 Getting Started with License Filebased Licensing FLEXnet Publisher Licensing Toolkit 11.5 P/N: FNP-115-GSLF01

2 Legal and Contact Information Part Number: P/N: FNP-115-GSLF01 Product Release Date: December 2007 Contacting Macrovision Macrovision Corporation 2830 De La Cruz Blvd. Santa Clara, CA Tel: (408) Fax: (408) For general information, technical support, the Macrovision knowledgebase, or to learn about consulting and training services, visit For the Macrovision Online Community, visit To access the RightAccess and RightCommerce Documentation Center, visit To access Installshield, Admin Studio, FLEXnet Connect, Update Service, or Install Anywhere documentation, visit Copyright Notice Copyright 2007 Macrovision Corporation and/or Macrovision Europe Ltd. All Rights Reserved. This product contains proprietary and confidential technology, information and creative works owned by Macrovision Corporation and its subsidiaries and their respective licensors. Any use, copying, publication, distribution, display, modification, or transmission of such technology in whole or in part in any form or by any means without the prior express written permission of Macrovision Europe Ltd. and Macrovision Corporation is strictly prohibited. Except where expressly provided by Macrovision Europe Ltd. and Macrovision Corporation in writing, possession of this technology shall not be construed to confer any license or rights under any of Macrovision Europe Ltd. and Macrovision Corporation s intellectual property rights, whether by estoppel, implication, or otherwise. ALL COPIES OF THE TECHNOLOGY and RELATED INFORMATION, IF ALLOWED BY MACROVISION CORPORATION, MUST DISPLAY THIS NOTICE OF COPYRIGHT AND OWNERSHIP IN FULL. This product incorporates software developed by others and redistributed according to license agreements. Copyright notices and licenses for these external libraries are provided in a supplementary document that accompanies this one. Trademarks Macrovision, AdminStudio, DemoNow, DemoShield, FLEXenabled, FLEXlm, FLEXnet, FLEXnet Certified, FLEXnet Connector, FLEXnet Manager, FLEXnet Publisher, Globetrotter, Hawkeye, InstallFromTheWeb, InstallShield, InstallShield Developer, InstallShield DevStudio, InstallShield Professional, It All Starts Here, OneClickInstall, Package For The Web, QuickPatch, ReadySell, RipGuard, SafeCast, Trymedia Systems, and Zero G Software are registered trademarks or trademarks of Macrovision Corporation in the United States of America and/or other countries. All other brand and product names mentioned herein are the trademarks and registered trademarks of their respective owners. Restricted Rights Legend The software and documentation are commercial items, as that term is defined at 48 C.F.R , consisting of commercial computer software and commercial computer software documentation, as such terms are used in 48 C.F.R or 48 C.F.R , as applicable. Consistent with 48 C.F.R or 48 C.F.R through , as applicable, the commercial computer software and commercial computer software documentation are being licensed to U.S. government end users (A) only as commercial items and (B) with only those rights as are granted to all other end users pursuant to the terms and conditions set forth in the Macrovision Corporation standard commercial agreement for this software. Unpublished rights reserved under the copyright laws of the United States of America.

3 Contents Legal and Contact Information Introduction to this Document What s New in this Document FLEXnet Publisher Licensing Toolkit Product Documentation Introduction to Licensing-File Based Licensing The FLEXnet Licensing Ecosystem FLEXnet Licensing Components License Model Overview Component Descriptions The License Request Process Evaluating FLEXnet Publisher Licensing Toolkit on Windows Identifying the Build Directories Evaluating the End-User Experience Unserved License Model Uncounted License File Using an Uncounted License File Served License Model Counted License File Configuring the Demo License Server as a Windows Service Starting the Demo License Server (using LMTOOLS) Checking the Status of the Demo License Server System Using a Served License Attempting to Checkout an Unlicensed Feature Stopping the Demo License Server (using LMTOOLS) Evaluating the Vendor Experience FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 3

4 Contents Licensing a Feature Editing the License File Re-signing the License File A Locked, Uncounted License Creating a Locked, Uncounted License Testing the License Security Considerations An Expiring License Building the FLEXnet Publisher Licensing Toolkit Setting Up the C Development Environment Configuring the FLEXnet Publisher Licensing Toolkit Changing TRL Strength Building the FLEXnet Publisher Licensing Toolkit Toolkit Resigning the Sample License File Conclusion Evaluating FLEXnet Publisher Licensing Toolkit on UNIX Identifying the Build Directories Evaluating the End-User Experience Viewing the Sample License Files Starting the Demo License Server System Checking the License Server System Status Running the Sample FLEXenabled Application Trying to Check Out an Unlicensed Feature Stopping the Demo License Server System Testing an Uncounted License Evaluating the Vendor Experience Licensing a Feature Editing the License File Re-signing the License File A Locked, Uncounted License Creating a Locked, Uncounted License Testing the License Security Considerations An Expiring License Building the FLEXnet Publisher Licensing Toolkit Configuring the FLEXnet Publisher Licensing Toolkit Changing TRL Strength Building the FLEXnet Publisher Licensing Toolkit Re-signing the Sample License File Conclusion License Models Basic License Models FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

5 Contents Node-locked/Uncounted Models Evaluation License Model Node-locked/Counted Models Floating Models License Model Modifiers Required License Model Modifiers Expiration Date Version Optional License Model Modifiers Usage-Based Licensing Mobile Licensing Deciding the Need for a License Server System Vendor Decisions Summary of Vendor Decisions Core Decisions Determining Licensable Product Configurations Hostid Support Checkout Failure Behavior Checkin Considerations Optional Diagnostic Handling License Server System Decisions Maintaining Consistency with the License Server System Connection/Reconnection Strategy Heartbeat Implementation Strategy License Sharing Checkin Considerations for Served Licenses License Server System Redundancy License Security Systems Overview Limiting Exposure Server-Side Exposure Product-Side Exposure License Signature Encryption Method Expiring Licenses Date Tampering HOSTID Choices Building the Product: Dynamic vs. Static Linking Tracking End-User Usage Usage Data Limitations License Fulfillment FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 5

6 Contents License Fulfillment Automated Fulfillment Other Methods Strategy for Delivering Rights Over Time Upgrading Incrementing Superseding Support Entitlement Transferring Rights - License Rehosting Evaluation Licensing Strategy Limited Time Demos Limited Functionality Demos Case Study Background FLEXnet Publisher Licensing Toolkit Use Case License Policy Definition Basic License Model License Model Modifiers Usage-Based Licensing Mobile Licensing License Server System Requirement Vendor Decisions Licensable Product Configurations Hostid Support Checkout Failure Behavior Checkin Considerations License Server System Consistency License Sharing Licensing Security License Fulfillment Usage Rights over Time License Rehosting Evaluation Licensing Strategy License File Location Sample License Certificates Evaluation Product Configuration Certificate Standard Product Configuration Certificate Updating the License Certificate Product Deliverables Glossary FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

7 Contents Index FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 7

8 Contents 8 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

9 Introduction to this Document This manual, FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing, describes the basic concepts of FLEXnet Licensing, license models, and concepts for designing license policies using License Files. To obtain a complete overview of the FLEXnet Publisher Licensing Toolkit capabilities, read this document and the companion document, Getting Started with Trusted Storage-based Licensing. This document contains the following chapters: Table -1: FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing Chapter Overview Topic Introduction to this Document Chapter 1, Introduction to Licensing-File Based Licensing Chapter 2, Evaluating FLEXnet Publisher Licensing Toolkit on Windows Chapter 3, Evaluating FLEXnet Publisher Licensing Toolkit on UNIX Chapter 4, License Models Chapter 5, Vendor Decisions Chapter 6, License Security Systems Content Provides an overview of the FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing, including Help Library conventions and usage. This chapter provides a general overview of FLEXnet Licensing using license rights held in license files. This chapter walks you though the process of evaluating FLEXnet Licensing behavior on Windows, both from the end-user s and the vendor s perspective. This chapter walks you though the process of evaluating FLEXnet Licensing behavior on UNIX, both from the end-user s and the vendor s perspective Gives a brief overview of FLEXnet Licensing and the basic steps for creating a license model. This chapter presents licensing policy concepts that you need to think about when designing a licensing policy for your product. Discusses license security, including issues and strategy for implementation. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 9

10 Chapter : Introduction to this Document What s New in this Document Table -1: FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing Chapter Overview Topic Chapter 7, License Fulfillment Chapter 8, Case Study Content Provides an overview of license fulfillment and installation at the end-user site. Presents a case study based on products and business strategies of a fictitious company, giving users insight into realistic FLEXnet Licensing scenarios. What s New in this Document The following chapters that were removed from version 11.4 of this document have been added back in: Chapter 2, Evaluating FLEXnet Publisher Licensing Toolkit on Windows Chapter 3, Evaluating FLEXnet Publisher Licensing Toolkit on UNIX The Windows FLEXnet Publisher Licensing Toolkit 11.5 requires a different installation procedure. Some instructions in Chapter 2, Evaluating FLEXnet Publisher Licensing Toolkit on Windows have been rewritten. FLEXnet Publisher Licensing Toolkit Product Documentation The following documents provide information about the FLEXnet Publisher Licensing Toolkit: Release Notes communicates information about changes to the application and supported thirdparty applications. Installation Guide describes how to install the Licensing toolkit. Getting Started with Trusted Storage-based Licensing is an introduction to FLEXnet Licensing using Trusted Storage. It includes step-by-step instructions for using example files provided within Licensing toolkits. These demonstrate how FLEXnet Licensing can be used to provide various licensing models. Getting Started with License File-based Licensing contains information for those software vendors new to FLEXnet Licensing using license file-based licensing. It includes an evaluation procedure that introduces these licensing concepts from both the software publisher and end-user s perspective. License File-based Programming Reference contains information about license file-base licensing. Certain information is relevant to both license file-based and trusted storage-based licensing. You should read this document and Getting Started with License File-based Licensing to understand the basic concepts of FLEXnet Licensing if you have not previously used it. Trusted Storage-based Programming Reference contains information licensing using Trusted Storage. If you have not previously used this capability, you should also read Getting Started with Trusted Storage-based Licensing to understand the basic concepts of FLEXnet Licensing using Trusted Storage. 10 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

11 Chapter : Introduction to this Document FLEXnet Publisher Licensing Toolkit Product Documentation Licensing for Java Programming Reference Guide contains guidelines for using the FLEXnet Publisher Licensing Toolkit for Java. License Administration Guide contains information the setup and administration of a licensing system, including setting up an options file and using Licensing utilities. Creating a Licensed Product: Setting up and Using the Development and Build Environment describes how to integrate the toolkit into the development environment, build a production licensing toolkit, and distribute a FLEXenabled application. C/C++ Function Reference summarizes and describes all publicly available C/C++ functions in the Licensing toolkit. Licensing for Java API Reference summarizes and describes all publicly available Java classes and methods in the Licensing for Java toolkit. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 11

12 Chapter : Introduction to this Document FLEXnet Publisher Licensing Toolkit Product Documentation 12 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

13 1 Introduction to Licensing-File Based Licensing FLEXnet Publisher Licensing Toolkit is a product licensing package that allows licensing a product on a per-computer basis (node-locked) as well as on a concurrent-usage basis (floating). FLEXnet Licensing using license files allows for the implementation of a wide variety of functionality within the licensing policy. General FLEXnet Licensing features include: A wide variety of licensing policy functionality and license styles, including, but not limited to: Node-locked licenses Demo licenses Personal-use licenses Floating licenses Counted and uncounted licenses Expiring licenses Administration tools for end-user license administrators Support for independent features from one or multiple vendors Several vendor-definable fields for each product feature Operation in a heterogeneous network of supported computer systems Transparent reconnection of the FLEXenabled product when its license server system becomes unavailable, including conditions of license server machine failure Simple configuration by using a single license file per network Configuration controls for system administrators FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 13

14 Chapter 1: Introduction to Licensing-File Based Licensing The FLEXnet Licensing Ecosystem The FLEXnet Licensing Ecosystem The FLEXnet Licensing ecosystem consists of: You, the vendor. You develop the license policy and enable your product with FLEXnet Publisher Licensing Toolkit. The end user. This is your customer to whom you deploy your FLEXenabled product and all related components. The FLEXnet Publisher Licensing Toolkit. The Licensing toolkit resides on a development machine at your site. You use it to integrate FLEXnet Licensing, via a client-side library, into your product, to generate license certificates, and to make customizations to the license server system. The FLEXnet Licensing components. This is your FLEXenabled product, in conjunction with the license certificate and other license model components, that you deploy at your end-user s site. FLEXnet Licensing Components This section presents: License Model Overview The FLEXnet Licensing components necessary for both unserved and served license models are presented. Component Descriptions A description of each license model component and the role it plays in your licensing policy. License Model Overview A major distinguishing characteristic of a license model is its requirements for a license server system. The need for a license server system stems from either a FLEXnet Publisher Licensing Toolkit requirement, your requirement, your end-user s requirement, or a combination of the three. The section titled Deciding the Need for a License Server System explores the requirements for license server systems in more depth. The Unserved License Model A license model that does not need a license server system has two components: The FLEXenabled Product A License Certificate Examples of this type of licence model include: expiring evaluation licenses; site licenses available to an unlimited number of users; and single-use, node-locked licenses. 14 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

15 Chapter 1: Introduction to Licensing-File Based Licensing FLEXnet Licensing Components Figure 1-1 shows this model. Each component is described in subsequent sections. FLEXenabled Product Your Product Code Licensing toolkit Client Library License Certificate Figure 1-1: FLEXnet Licensing Unserved License Model Components Implementing your licensing policy for unserved licenses requires you to: Instrument your product with calls to the FLEXnet Publisher Licensing Toolkit client library Create a license certificate with keywords appropriate to your license model For an unserved license, the FLEXenabled product and license certificate reside on the same machine. The Served License Model For served licenses, there are four required FLEXnet Licensing components: The FLEXenabled Product The FLEXnet License Server Manager daemon, lmgrd The Vendor Daemon, which, along with the license server manager, comprises the license server system A License Certificate In addition to the four required components, there are three optional components: Debug Log File End-User Administration Options File Report Log File Served licenses allow a fixed number of concurrent users access to your application at any one time. The server keeps track of the number of concurrent users. The licenses are not node-locked to a specific machine, but rather, float on the network, allowing network wide usage. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 15

16 Chapter 1: Introduction to Licensing-File Based Licensing FLEXnet Licensing Components Figure 1-2 shows the relationship these components have to one another. Each component is described in subsequent sections. FLEXenabled Product Your Product Code Licensing toolkit Client Library TCP/IP Port License Server System Components License Server FLEXnet Licensing License Server Manager Vendor Daemon License Certificate Debug Log File Administration Options File Report Log File Figure 1-2: FLEXnet Licensing Served License Model Components Implementing your licensing policy for served licenses requires you to: Instrument your product with calls to the FLEXnet Publisher Licensing Toolkit client library Configure a vendor daemon Create a license certificate with keywords appropriate to your license model The license server system components can reside on the same machine as the FLEXenabled product; but typically, they reside on a machine in the network and communicate with the product via a TCP/IP port. The end user enables the Debug and Report logs, and configures the FLEXnet Publisher Licensing Toolkit end-user Administration Options file. Component Descriptions The FLEXenabled Product The FLEXenabled product is your product instrumented with calls to the FLEXnet Publisher Licensing Toolkit client library. The Licensing toolkit client library provides routines that establish the productside licensing policy, read the license file, and, in the case of served licenses, provide communication with the license server system. This ultimately results in granting or denying usage. License Certificate The license certificate is created by the product vendor. It is installed as a license file by the end-user license administrator or can be installed automatically as part of the product installation process. It contains at least one line of data (called a FEATURE or INCREMENT line) for each FLEXenabled product configuration. Each FEATURE line contains a license key or signature based on the data in that line. 16 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

17 Chapter 1: Introduction to Licensing-File Based Licensing FLEXnet Licensing Components For a served license model, information about the license server machines, their hostids, and vendor daemons are specified with SERVER and VENDOR lines. A FLEXenabled product implementing an unserved license model need only read a valid license file to run it does not need a license server system. The FLEXnet License Server Manager The FLEXnet license server manager, lmgrd, handles the initial contact with the FLEXenabled product, passing the connection on to the appropriate vendor daemon. It also starts and restarts the vendor daemon. The Vendor Daemon In FLEXnet Licensing, served licenses are granted by processes running on the license server machine. There is one process specific for each vendor who has a FLEXenabled product on the network. This process is called the vendor daemon. The vendor daemon keeps track of how many of its licenses are checked out, and who has them. A FLEXenabled product communicates with a vendor daemon, usually through TCP/IP network communications. The FLEXenabled product and the daemon processes (the license server system) can run on separate machines on your network, across any size wide-area network. Also, the format of the traffic between the FLEXenabled product and the vendor daemon is machine independent, allowing for heterogeneous networks. This means the license server system and the computer running a product can be either different hardware platforms or even different operating systems (Windows and UNIX, for example). Debug Log File A debug log file contains status and error messages useful for debugging the license server system. Some of the debug log output describes events specific to lmgrd and some of the debug log output describes events specific to a vendor daemon. End-User Administration Options File The options file allows the end-user license administrator to control various operating parameters of FLEXnet Licensing within the limits of the product s licensing policy. Specifically, the license administrator can: Administer named-user and named-host licenses: Allowing features to be used by specific users/hosts/groups Denying feature use to specific users/hosts/groups Reserve licenses for specific users/hosts/groups Restrict the number of licenses available Control the amount of information logged about license usage Enable a report log file FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 17

18 Chapter 1: Introduction to Licensing-File Based Licensing FLEXnet Licensing Components Report Log File The report log file contains feature usage information and is generated by the vendor daemon. Report log output is encrypted and is utilized by reporting products such as FLEXnet Manager. The License Request Process Served License Model When the FLEXenabled application runs in the context of a served license model, the following occurs: 1. The license module in the FLEXenabled application finds the license file, which includes the host name of the license server machine and TCP/IP port number of the license server manager, lmgrd. 2. The FLEXenabled application establishes a connection with the license server manager (lmgrd) and tells it what vendor daemon it needs to talk to. 3. lmgrd determines which machine and TCP/IP port correspond to the master vendor daemon and sends that information back to the FLEXenabled application. 4. The FLEXenabled application establishes a connection with the specified vendor daemon and sends its request for a license. 5. The vendor daemon checks in its memory to see if any licenses are available and sends a grant or denial back to the FLEXenabled application. 6. The FLEXnet Publisher Licensing Toolkit client library routines in the application grants or denies use of the feature, as appropriate. Unserved License Model Unserved license models depend solely on the Licensing toolkit client library routines in the application to grant or deny usage based solely upon the contents of the license file. 18 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

19 2 Evaluating FLEXnet Publisher Licensing Toolkit on Windows This chapter walks you though the process of evaluating FLEXnet Licensing behavior using license files on Windows, both from the end-user s and the vendor s perspective. Before you start this chapter, please install the FLEXnet Publisher Licensing Toolkit as described in the instructions in the Installation Guide. The Licensing toolkit contains these pre-built files used to evaluate FLEXnet Licensing: Sample license files (counted.lic, expired.lic, and uncounted.lic) Sample vendor daemon (demo.exe) Toolkit Test Program, a sample FLEXenabled application (lmflex.exe) License generation utility (lmcrypt.exe) FLEXnet Publisher Licensing Toolkit utilities (lmtools.exe) DEMO license server system The demo vendor keys provided to you by Macrovision are used later in this chapter. If your demo vendor keys expire before you complete this evaluation, contact your salesperson at Macrovision. Note: Microsoft Visual C++ version 6.0 or.net is required for part of this evaluation. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 19

20 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Identifying the Build Directories Identifying the Build Directories The procedures in this chapter assume you have installed the Licensing toolkit. Table 2-1 lists the directories that are involved in the evaluation exercises along with their shortcuts. Take a few moments to identify the location of each shortcut for your particular installation before proceeding: the shortcuts are used throughout this chapter. Table 2-1: Toolkit Directories Shortcut Name install_dir platform machind Default Location No default, you define this path at installation time. <install_dir>\<platform_identity> An example of a <platform_identity> is i86_n3 <install_dir>\machind Now you are ready to begin your evaluation of FLEXnet Licensing. All operations take place in the platform directory unless otherwise noted. Evaluating the End-User Experience The evaluation steps in this section take you through different actions that an end user or license administrator at your end-user s site may take. Typical scenarios are demonstrated in the following sections: Using an Uncounted License File Configuring the Demo License Server as a Windows Service Starting the Demo License Server (using LMTOOLS) Checking the Status of the Demo License Server System Using a Served License Attempting to Checkout an Unlicensed Feature Stopping the Demo License Server (using LMTOOLS) All components required to perform the steps in this section are prebuilt and have been placed on your system during installation. Unserved License Model This demonstration of the unserved license model uses two example components provided in the toolkit in install_dir\platform : The sample Licensing toolkit Test Program - lmflex.exe 20 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

21 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the End-User Experience A sample uncounted license file - uncounted.lic Uncounted License File Open the sample uncounted license file, install_dir\platform\uncounted.lic, in a text editor. You see something like this output: # an uncounted license FEATURE f2 demo permanent uncounted HOSTID=ANY \ SIGN=" C50 609D 13F4 353F 4866 A D \ 05F9 2D83 2B0C A15F" This license is for feature f2. It is licensed to the vendor demo. It is a permanent license, that is it will not expire. It is uncounted and therefore it does not need a license server system. It is valid on any machine as HOSTID=ANY. The following figure shows where these items are located in the license file. Figure 2-1: Uncounted License File Using an Uncounted License File Follow the steps below to start the Test Program, install_dir\platform\lmflex.exe, and use it to check out a license for the feature f2 from the uncounted.lic license file. Task To check out a license for feature f2: 1. Open a command window and change to the platform folder. In this window, type lmflex. You see: Enter "f1" to demo floating functionality Enter "f2" to node-locked functionality Enter feature to checkout [default: "f1"]: 2. Type f2 and press Enter to check out a license for feature f2. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 21

22 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the End-User Experience 3. If you have not used the licensing toolkit on this machine before, the following dialog is displayed: Use the FLEXnet License Finder dialog to specify the uncounted.lic license file as follows: a. Click Specify the License File and click Next. b. Type uncounted.lic and click Next. c. Click Finish. 4. The following message is displayed, confirming that a license for feature f2 has been checked out: f2 checked out...press return to exit Press Enter to check the f1 license back in and exit lmflex. Note that step 3 is required because lmflex does not specify the location of the license file, but instead relies on a license server system searching for license files in its local directory. When a license file has been used to successfully checkout a license, the path to the license file is stored in the registry. This path will be used subsequently when searching for a license. Served License Model This demonstration of the served license model uses the following components provided in the toolkit: The sample Licensing toolkit Test Program - install_dir\platform\lmflex.exe A sample counted license file - install_dir\platform\counted.lic DEMO license server system - demo.exe and lmgrd Tool for managing license server systems - LMTOOLS Macrovision provides tools for managing license server systems that you can distribute to your customers. On Windows, Macrovision provides lmutil.exe, a set of command-line utilities, and LMTOOLS, a similar set of utilities with a graphical user interface which is used in this demonstration. 22 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

23 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the End-User Experience Counted License File Open the sample counted license file, install_dir\platform\counted.lic, in a text editor. You see something like this output: SERVER this_host ANY VENDOR demo FEATURE f1 demo 1.0 permanent 4 SIGN="AADD B062 54D1 47E3 \ 1FF6 145F 59CE FE69 0FBC 0000 AA10 FFB3 6EB3" This sample license file is valid on any machine (because on the SERVER line the server hostid is ANY ). It contains one FEATURE line for f1 that has a license count of 4 and is served by the vendor daemon demo. The following diagram shows where these items are located on the FEATURE line. Figure 2-2: Counted FEATURE line Configuring the Demo License Server as a Windows Service The machine on which the license server system is installed is normally set up so that the license server system is run as a service and automatically started when the machine is started. This section gives instructions on how to configure the demo license server system as a service using the toolkit utility LMTOOLS. To configure a license server system as a service, you must have Administrator privileges. Task To configure the demo license server system as a service: 1. From the platform directory double-click lmtools.exe. This runs LMTOOLS. 2. Click the Configuration using Services button, and then click the Config Services tab. 3. In the Service Name, type the name of the service. It is recommended that you choose a service name that includes the toolkit version, for example 11.4 DEMO License Manager. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 23

24 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the End-User Experience 4. In the Path to the lmgrd.exe file field, enter or browse to the lmgrd.exe provided in this toolkit. 5. In the Path to the license file field, enter or browse to the license file that is used to start up this license server system. Ensure that you choose a license file that was generated for use with the Demo vendor daemon, for example counted.lic from the toolkit platform directory. 6. In the Path to the debug log file, enter or browse to the debug log file that this license server system writes. Prepending the debug log file name with the + character appends logging entries. The default location for the debug log file is the c:\winnt\system32 folder. To specify a different location, make sure you specify a fully qualified path. 7. Check Use Services. Figure 2-3: Completed example LM_TOOLS Config Services screen 8. To save the service, click Save Service. Note that for this evaluation the demo license server system is started manually. Normally a license server system is set to start automatically when the machine is switched on. To configure this, at step 7 check Use Services and Start Server at Power Up. Starting the Demo License Server (using LMTOOLS) Task To start the demo license server using LMTOOLS: 1. From the platform directory double-click lmtools.exe. 2. Click the Start/Stop/Reread tab. 24 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

25 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the End-User Experience 3. Select the demo license server service name (see step 3 in Configuring the Demo License Server as a Windows Service). 4. Click Start Server. Checking the Status of the Demo License Server System Use LMTOOLS to check the status of the demo license server system and determine: Whether it is running Number of licenses issued Number of licenses in use Users of each FLEXenabled feature Task To check the license server system status: 1. In LMTOOLS, click the Server Status tab. 2. Click Perform Status Enquiry. 3. Scroll down the display; you should see output similar to that shown below: demo: UP v11.4 Feature usage info: Users of f1: (Total of 4 licenses issued; Total of 0 licenses in use) FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 25

26 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the End-User Experience Note that no users have any of the licenses for f1 checked out. Using a Served License Follow the steps below to start the Test Program, lmflex.exe, and use it to check out a license for the feature f1 from the counted.lic license file. To complete this section you must have completed the previous sections and the demo license server system must be running. Task To demonstrate the use of a served license: 1. Open a command window and change to the platform folder. In the this window, type lmflex. You see: Enter "f1" to demo floating functionality Enter "f2" to node-locked functionality Enter feature to checkout [default: "f1"]: 2. Press Enter to check out a license for feature f1. The following confirmation message is displayed: f1 checked out...press return to exit To check the status of the license server system with a license checked out, in the Server Status pane of LMTOOLS, click Perform Status Enquiry. Scroll down to see output with user, host, and display information about the f1 license that you just checked out: demo: UP v11.4 Feature usage info: Users of f1: (Total of 4 licenses issued; Total of 1 license in use) "f1" v1.0, vendor: demo floating license daniel myhost myhost (v1.0) (myhost/ ), start View the tail of the debug log file, platform\demo.dl, by clicking the Config Services tab and clicking the View Log button. A viewer opens and you should see something like: 19:03:54 (demo) OUT:"f1" daniel@myhost 5. In the Config Services tab, click the Close Log button to close the debug log viewer. 6. In the command window, press Enter to check the f1 license back in and exit lmflex. 7. Use LMTOOLS t0 check the server status again to see that now no licenses are checked out. Attempting to Checkout an Unlicensed Feature 1. Run lmflex again, and instead of selecting the default feature f1 for which you have a license, type f3 as the feature to check out. 2. An error dialog appears telling you that the feature does not exist. Click OK in the dialog. 26 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

27 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the Vendor Experience Stopping the Demo License Server (using LMTOOLS) 1. In the Start Stop Reread tab of LMTOOLS, click Stop Server. 2. Check the license server system status now that you have stopped the DEMO license server system. You see: lmgrd is not running: Cannot connect to license server The server (lmgrd) has not been started yet, or the wrong or license file is being used, or the port or hostname in the license file has been changed. 3. Look at the license server system debug log file at platform\lmgrd.dl to review the activity of the DEMO license server system. Evaluating the Vendor Experience This section of the evaluation demonstrates some of the activities you perform in the course of implementing your license policy. The versatility of FLEXnet Licensing s policy in the license is showcased in the following subsections: Licensing a Feature A Locked, Uncounted License An Expiring License Building the FLEXnet Publisher Licensing Toolkit Now, proceed to the next sections for a demonstration of FLEXnet Licensing s policy in the license technology. Licensing a Feature Editing the License File In order to give yourself a license for feature f3, the sample license file must be edited. Follow the steps below to edit the license by replacing the feature to be licensed. Task To edit the sample license file: 1. Open install_dir\platform\counted.lic in a text editor. 2. Duplicate the f1 FEATURE line at the bottom of the file. 3. On the second f1 FEATURE line, replace f1 with f3. 4. Save and close counted.lic. 5. Click the Start Stop Reread tab in LMTOOLS. Select DEMO License Manager and click the Start Server button. This starts the license server system and forces the edited license file to be read. Wait a few seconds for the server to start. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 27

28 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the Vendor Experience 6. Start lmflex and try to check out f3 again. 7. You see an error dialog indicating you cannot check out the license. You added an f3 FEATURE line in the license file by copying it from f1 and simply changing the feature name. However, the signature is still authenticated for feature f1 at that point. In the next section, you re-sign the certificate so it is authenticated for f3. Click OK in the error dialog. Re-signing the License File In the last section, you saw that it is not possible to simply edit the license file, as an end user may try to do, to create a FEATURE line for f3. Now, generate a license file with valid FEATURE lines for both f1 and f3 with lmcrypt. Task To re-sign the license file: 1. Open a command-line window and change to the platform folder. In this window, type lmcrypt counted.lic. The license file should now resemble that shown below: SERVER this_host ANY VENDOR demo FEATURE f1 demo 1.0 permanent 4 SIGN="AADD B062 54D1 47E3 \ 1FF6 145F 59CE FE69 0FBC 0000 AA10 FFB3 6EB3" FEATURE f3 demo 1.0 permanent 4 SIGN="CDFE \ AD DEFE 8FDD 0000 ADDE FFB3 3545" 2. Click the Start Stop Reread tab in LMTOOLS. Click the ReRead License File button to tell the license server system to reread its edited license file. 3. Run lmflex again and try to check out f3. Now that you have a valid license for f3, you are able to check out a license for it. 4. When you are finished experimenting in the Start Stop Reread pane of LMTOOLS, click the Stop Server button. 5. Exit lmflex. A Locked, Uncounted License This section takes you through the process of locking a license to a specific machine simply by regenerating the FEATURE line within the license file, which incorporates the HOSTID into the license signature. There is no need to modify either the Licensing toolkit or application to incorporate this license policy. The steps below demonstrate how to node-lock the license for feature f2 to your specific machine. 28 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

29 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the Vendor Experience Creating a Locked, Uncounted License Task To retrieve the hostid for your machine: If not already running, start LMTOOLS and select the System Settings tab. The various types of hostids supported on the Windows platform are displayed in the Hostid Settings box. For this demonstration, use the value for Ethernet Address. If multiple ethernet addresses exist, pick one. Alternatively, use the FLEXnet Publisher Licensing Toolkit command line utility, lmutil. Open a command-line window and change to the platform folder. In this window, type lmutil lmhostid. It displays the default hostid for your machine. For Windows platforms, this is the ethernet address: lmutil - Copyright (c) Macrovision Europe Ltd. and/or by Macrovision Corporation. All rights reserved. The FLEXnet host ID of this machine is "000103e686e6" Task To create the license: 1. You write over uncounted.lic during this sequence, so copy it to a file called uncounted_lic.orig. 2. In the platform directory, open uncounted.lic in a text editor. 3. Locate the FEATURE line for feature f2 and replace the current hostid, ANY, with the value of your machine s hostid. The feature line now looks something like: FEATURE f2 demo permanent uncounted HOSTID=000103e686e6 SIGN="A1C6...52A3" 4. Re-sign the license file to incorporate the new hostid into the license signature by typing lmcrypt uncounted.lic. Testing the License Run lmflex and try to check out feature f2. A license for feature f2 is successfully granted because the application is executing on the machine to which the license is locked. Check in the feature f2. Because the license file for f2 is in the same directory as lmflex and has an extension of.lic, its license is found and used. Additionally, the license for f2 is uncounted; it does not need a license server system to allow it to run. Security Considerations As previously mentioned, the hostid value is incorporated in the license signature and is used in license authentication. Any changes to the license signature, the license HOSTID= value, or the actual machine hostid invalidates the license; the FLEXenabled application will fail to authenticate the license and any license requests fail. To demonstrate this concept, follow the steps below. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 29

30 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the Vendor Experience Task To demonstrate security considerations: 1. In the platform directory, open uncounted.lic in a text editor. 2. Locate the FEATURE line for feature f2 and modify the value of the HOSTID= keyword to a bogus value, simulating an unauthorized attempt to rehost the license. The feature line now looks something like: FEATURE f2 demo permanent uncounted HOSTID=000103e6 SIGN="A1C6...52A3" 3. Do not re-sign the license. 4. Run lmflex and try to check out feature f2. A FLEXnet Licensing error dialog box appears to indicate that the license request is denied because the application detects the inconsistency between the HOSTID= value in the feature line and that of the actual machine used to create the signature. Click OK in the error dialog. This last sequence demonstrates FLEXnet Licensing s policy in the license technology. You, the vendor, define the policy in this case, locked to a specific machine and create the license. You are in control of the license usage until you change it. An Expiring License This section demonstrates an expiring license policy. To implement it, simply set an expiration date in the FEATURE line; there is no need to modify either the Licensing toolkit or application. Then, when the license is signed, the expiration date is incorporated into the license signature. In the steps below, you modify the expiration date of the locked feature f4 located in the expired.lic license file. The expiration date is included in the license signature and is used in license authentication. Simply moving the expiration date forward will not create a legitimate license; the FLEXenabled application will fail to authenticate the license and any license requests fail. Task To demonstrate an expiring license policy: 1. Run lmflex and try to get a license for feature f4. The license request is denied because the license has expired. 2. You write over expired.lic during this sequence, so copy it to a file called expired_lic.orig. 3. Open expired.lic in a text editor. 4. Locate the FEATURE line for feature f4 and modify the expiration date to a date in the future. The feature line now looks similar to the example shown below: FEATURE f4 demo dec-2010 uncounted HOSTID=ANY SIGN="A1C6...52A3" 5. Save and close expired.lic. Do not resign the license. 6. Run lmflex and try to check out feature f4. Since the expiration date is now different to that encoded in the license signature, a FLEXnet Licensing error dialog box appears to indicate that the license 30 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

31 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the Vendor Experience request is denied this time because the signature cannot be authenticated. Click OK in the error dialog. 7. Now, re-sign the license file to incorporate the new hostid into the license signature by typing lmcrypt expired.lic. 8. Run lmflex and try to check out feature f4. A license for feature f4 is successfully granted because the license has not expired. Because the license file for f4 is in the same directory as lmflex and has an extension of.lic, its license is found and used. Additionally, the license for f4 is uncounted; it does not need a license server system to allow it to run. 9. Exit lmflex, this checks in the license for feature f4. Building the FLEXnet Publisher Licensing Toolkit In this section, you will rebuild the FLEXnet Publisher Licensing Toolkit to change the strength of tamper-resistant licenses (TRL) authentication from 113 bits to 163 bits. TRL uses public-key technology from Certicom to make the signatures on FEATURE/INCREMENT lines more difficult to counterfeit. As shipped, the Licensing toolkit is shipped with TRL enabled at the 113-bit strength, denoting a public-key length of 113 bits. First, take a look at the FEATURE lines in counted.lic, for instance, the line for feature f1. They resemble: FEATURE f1 demo 1.0 permanent 4 SIGN="003D B054 54D1 47E3 1FF6 \ 145F 59CE FE69 0FBC F4FF AA10 EEB3 6EB3" Observe the length of the signature value for the SIGN= keyword. Setting Up the C Development Environment Note: To build the FLEXnet Publisher Licensing Toolkit, you must use Microsoft Visual C++ version 6.0, version 7.0 or version 8.0. Visual C++ version 7 is shipped as part of Visual Studio.NET 2003 The Licensing toolkit is built using command-line tools rather than the Microsoft Visual C++ integrated development environment (IDE). Make sure that you have the command-line interface of the Microsoft Visual C++ development environment correctly configured. Consult the Visual C++ documentation for details about building from the command line. Configuring the FLEXnet Publisher Licensing Toolkit Up until now, you used the prebuilt FLEXnet Licensing components for this evaluation. As shipped, the Licensing toolkit is in an unconfigured state. You must configure it in order to rebuild it. You use your demo vendor keys provided to you by Macrovision for the following configuration procedure. 1. Change directories to the machind folder. 2. Open lm_code.h in a text editor. Find the lines similar to the following lines: FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 31

32 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the Vendor Experience #define VENDOR_KEY1 0x0 #define VENDOR_KEY2 0x0 #define VENDOR_KEY3 0x0 #define VENDOR_KEY4 0x0 #define VENDOR_KEY5 0x0 3. Replace all five lines with the demo vendor key lines that you received from Macrovision. If your demo vendor keys have expired, contact your salesperson at Macrovision. 4. Keep lm_code.h open. Changing TRL Strength Task To change the TRL strength: 1. In lm_code.h, find the definition of LM_STRENGTH that looks similar to: #define LM_STRENGTH LM_STRENGTH_113BIT 2. Redefine LM_STRENGTH to specify 163-bit strength. The definition should look like #define LM_STRENGTH LM_STRENGTH_163BIT 3. Leave TRL_KEYs set to 0x0. They do not get set when using demo vendor keys. 4. Save and close lm_code.h. Building the FLEXnet Publisher Licensing Toolkit Toolkit For your changes to take effect, you need to build the Licensing toolkit. Make sure lmflex is closed and the license server system is stopped before you attempt to rebuild the Licensing toolkit. To build your Licensing toolkit, in a command window, change to the platform folder and type build. The build.bat file calls nmake. You now have a demo Licensing toolkit that supports TRL at the 163-bit strength level. Since this modification changes the authentication method, all components, including the sample application, lmflex, have been rebuilt. Resigning the Sample License File Now, regenerate the license file to create license signatures which support TRL authentication at the 163-bit level. 1. Copy counted_orig.lic into counted.lic. 2. In the platform directory, type lmcrypt counted.lic. 3. Open counted.lic in a text editor and look at the FEATURE line for feature f1. You should see lines similar to those shown below: FEATURE f1 demo 1.0 permanent 4 SIGN="01C D AE6C 92CB 0360 \ 1124 AC73 B79B 1785 C C EAAF DF 0FAF 786A \ AA19 E123 52A3" 32 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

33 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Conclusion 4. Observe the length of the signature and compare it to the line before you started. 5. Close counted.lic. Conclusion You have completed the evaluation of FLEXnet Publisher Licensing Toolkit on Windows. When you are ready to build your Licensing toolkit with your production vendor keys, see Creating a Licensed Product: Setting up and Using the Development and Build Environment. If you want to evaluate FLEXnet Publisher Licensing Toolkit on UNIX, see Evaluating FLEXnet Publisher Licensing Toolkit on UNIX. Remember to set LM_STRENGTH to an appropriate value before you build your production Licensing toolkit. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 33

34 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Conclusion 34 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

35 3 Evaluating FLEXnet Publisher Licensing Toolkit on UNIX This chapter walks you though the process of evaluating FLEXnet Licensing behavior on UNIX, both from the end-user s and the vendor s perspective. Before you start this chapter, please install the FLEXnet Publisher Licensing Toolkit as described in the instructions in the Installation Guide. The Licensing toolkit is installed on your system and contains these prebuilt files used to evaluate FLEXnet Licensing: Sample license files (counted.lic, expired.lic, and uncounted.lic) Sample vendor daemon (demo) Toolkit Test Program, a sample FLEXenabled application (lmflex) License generation utility (lmcrypt) FLEXnet Publisher Licensing Toolkit utilities (lmutil) DEMO license server system The demo vendor keys provided to you by Macrovision are used later in this chapter. If your demo vendor keys expire before you complete this evaluation, contact your salesperson at Macrovision. Note: A C development environment is required for part of this evaluation. Consult the FLEXnet Publisher Licensing Toolkit Release Notes for your platform s C development environment requirements. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 35

36 Chapter 3: Evaluating FLEXnet Publisher Licensing Toolkit on UNIX Identifying the Build Directories Identifying the Build Directories The procedures in this chapter assume you have installed the FLEXnet Publisher Licensing Toolkit. Table 3-1 lists the directories that are involved in the evaluation exercises along with their shortcuts. Take a few moments to identify the location of each shortcut for your particular installation before proceeding; the shortcuts are used throughout this chapter. Table 3-1: Toolkit Directories Shortcut Name install_dir platform machind Default Location No default, you define this path at installation time. <install_dir>/<platform_identity> For example, the platform directory is i86_re3 for the Red Hat Enterprise Linux on x86 platform. <install_dir>/machind Now you are ready to begin your evaluation of FLEXnet Publisher Licensing Toolkit on UNIX. Evaluating the End-User Experience The evaluation steps in this section take you through different actions that an end user or license administrator at your end-user s site may take. Typical scenarios are presented for starting the license server system, checking its status, and checking out licenses for features in the demo FLEXenabled application. All components necessary to perform the steps in this section are prebuilt and have been placed on your system during installation. Viewing the Sample License Files A sample license file, counted.lic, is shipped in the platform folder and was used to set up a DEMO license server system when you installed the FLEXnet Publisher Licensing Toolkit. Task To view the sample license files: 1. View the contents of counted.lic. You see something like: SERVER this_host ANY VENDOR demo FEATURE f1 demo 1.0 permanent 4 SIGN="AADD B062 54D1 47E3 \ 1FF6 145F 59CE FE69 0FBC 0000 AA10 FFB3 6EB3" 2. You write over counted.lic during this demo, so copy it to a file called counted_lic.orig. This sample license file is valid on any machine (because on the SERVER line the server hostid is ANY ). It contains one FEATURE line for f1 that has a license count of 4 and is served by the vendor daemon demo. Figure 3-1 shows the location of these items in the FEATURE line. 36 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

37 Chapter 3: Evaluating FLEXnet Publisher Licensing Toolkit on UNIX Evaluating the End-User Experience Figure 3-1: FEATURE Line 3. View the contents of uncounted.lic. You see something like: # an uncounted license FEATURE f2 demo permanent uncounted HOSTID=ANY \ SIGN=" C50 609D 13F4 353F 4866 A D \ 05F9 2D83 2B0C A15F" This license for f2 is uncounted and therefore does not require a license server system to check it out. Starting the Demo License Server System A FLEXnet license server system is composed of an lmgrd process and one or more vendor daemons (in this case, the demo vendor daemon). In this section, you learn how to start the demo license server system. The license server system keeps track of the usage count, so it is necessary to start the license server system in order to serve the licenses. The steps below use the license for feature f1 in counted.lic. This license has a count of four, meaning that a maximum of four users can concurrently use the feature. 1. Set the license file path that the demo vendor daemon uses to the platform directory: setenv DEMO_LICENSE_FILE platform 2. To start the demo license server system, change to the platform directory and type lmgrd -c counted.lic. After lmgrd starts, it starts the demo vendor daemon. The license server system (lmgrd and demo) write their debugging output to the window where you started lmgrd because the license server system is started without specifying a debug log. 3. After you start lmgrd, the output of the license server system looks like: 11:11:49 (lmgrd) FLEXnet Licensing (11.4) started on myhost (Sun) (5/23/2007) 11:11:49 (lmgrd) FLEXnet Licensing Copyright , Macrovision Corporation 11:11:49 (lmgrd) US Patents 5,390,297 and 5,671, :11:49 (lmgrd) World Wide Web: 11:11:49 (lmgrd) License file(s): counted.lic 11:11:49 (lmgrd) lmgrd tcp-port FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 37

38 Chapter 3: Evaluating FLEXnet Publisher Licensing Toolkit on UNIX Evaluating the End-User Experience 11:11:49 (lmgrd) Starting vendor daemons... 11:11:49 (lmgrd) Started demo (internet tcp_port pid 9159) 11:11:49 (demo) FLEXnet Licensing version :11:49 (demo) License server system started on myhost for: f1 4. Open another window and change to the platform directory (for example, sun4_u5). Leave the first window open to monitor the output of lmgrd and the demo vendor daemon. Checking the License Server System Status Now, check the status of the license server system to determine Whether it is running Number of licenses issued Number of licenses in use Users of each FLEXenabled feature To check the license server system status, in the platform directory, type lmstat -a -c counted.lic. You should see output similar to that shown below: License server system status: License file(s) on myhost: install_dir/sun4_u5/ counted.lic: myhost: license server system UP (MASTER) v11.4 Vendor daemon status (on myhost): demo: UP v11.4 Feature usage info: Users of f1: (Total of 4 licenses issued; Total of 0 licenses in use) Note that none of the four licenses for f1 are in use. Running the Sample FLEXenabled Application Start the sample FLEXenabled application, lmflex, and use it to check out a license for the feature f1. 1. Set the link library path to the current directory: % setenv LD_LIBRARY_PATH platform 2. In the platform directory, type lmflex. You see: Enter "f1" to demo floating functionality Enter "f2" to node-locked functionality Enter feature to checkout [default: "f1"]: 3. Press Enter to check out a license for feature f1.the following confirmation message is displayed: f1 checked out...press return to exit Check the tail of the license server system output to see the checkout of f1. 11:22:35 (demo) OUT:"f1" daniel@myhost 5. In a third window, change to the platform directory. To check the status of the license server system with a license checked out, in the third window, again type lmstat -a -c counted.lic. You see output with user, host, and display information about the f1 license that you just checked out: 38 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

39 Chapter 3: Evaluating FLEXnet Publisher Licensing Toolkit on UNIX Evaluating the End-User Experience Users of f1: (Total of 4 licenses issued; Total of 1 license in use) "f1" v1.0, vendor: demo floating license daniel myhost (v1.0) (myhost/ ), start Wed 5/23 11:22 6. Close the window where you just ran lmstat. 7. Press Enter to check the f1 license back in and exit lmflex. 8. Check the tail of the license server system output to see the checkin of f1: 11:23:40 (demo) IN:"f1" daniel@myhost Trying to Check Out an Unlicensed Feature 1. Run lmflex again, and instead of selecting the default feature f1 for which you have a license, type f3 as the feature to check out. You see that the checkout failed because f3 is not supported by the license server system: Checkout failed: License server system does not support this feature Feature: f3 License FLEXnet Licensing error: -18,147 For further information, refer to the FLEXnet Licensing End User Guide, available at " Stopping the Demo License Server System When you are done experimenting with lmflex and your license file, stop the license server system. 1. In the platform directory, type lmdown -c counted.lic. You see a description of the license server system and a request for confirmation: Port@Host Vendors 1) 27000@myhost demo Are you sure (y/n)? 2. Confirm that you want to shut down the demo license server system by typing y. 3. Look at the tail of the license server system output: 11:35:46 (lmgrd) SHUTDOWN request from daniel at node myhost 11:35:46 (lmgrd) lmgrd will now shut down all the vendor daemons 11:35:46 (lmgrd) Shutting down demo 11:35:46 (demo) daemon shutdown requested - shutting down 11:35:46 (lmgrd) Shut down FLEXnet demo server on node myhost Testing an Uncounted License Remember that you started the demo license server system to be able to check out a counted f1 license. Now, observe the difference in the behavior of f1 and f2 now that the demo license server system is not running. 1. Run lmflex again, and press Enter to check out a license for feature f1. 2. You see that the checkout failed because the license server system is not running on THIS_HOST: FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 39

40 Chapter 3: Evaluating FLEXnet Publisher Licensing Toolkit on UNIX Evaluating the Vendor Experience Checkout failed: Network connect to THIS_HOST failed The license file indicates THIS_HOST, and the server is not running on this host. If it's running on a different host, THIS_HOST should be changed to the correct host. Feature: f1 License path: counted.lic:expired.lic:uncounted.lic FLEXnet Licensing error: -95,378. System Error: 146 "Connection refused" For further information, refer to the FLEXnet Licensing End User Guide, available at " 3. Now rerun lmflex, this time replacing f1 with f2 and press Enter to check out a license for feature f2. Remember that the license for f2 is uncounted and locked and is located in uncounted.lic. Because the license file for f2 is in the same directory as lmflex and has an extension of.lic, its license is found and used. Additionally, the license for f2 is uncounted; it does not need a license server system to allow it to run. 4. Press Enter to check the f2 license back in. Evaluating the Vendor Experience This section of the evaluation demonstrates some of the activities you perform in the course of implementing your license policy. The versatility of FLEXnet Licensing s policy in the license is showcased in the following subsections. Licensing a Feature A Locked, Uncounted License An Expiring License Building the FLEXnet Publisher Licensing Toolkit Now, proceed to the next sections for a demonstration of FLEXnet Licensing s policy in the license technology. Licensing a Feature Editing the License File Now, edit the sample license file to try to give yourself a license for feature f3. 1. Open counted.lic in a text editor. 2. Duplicate the f1 FEATURE line on the line below. This FEATURE line spans multiple physical file lines in the file; make sure you capture the entire line. 3. On the second FEATURE line, replace f1 with f3. 4. Save and close counted.lic. 5. If it is not already running start the demo license server system; in the platform directory, type lmgrd -c counted.lic. This starts the license server system and forces the edited license file to be read. Wait a few seconds for the server to start. 40 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

41 Chapter 3: Evaluating FLEXnet Publisher Licensing Toolkit on UNIX Evaluating the Vendor Experience 6. Open another window and change to the platform directory. Leave the first window open to monitor the output of lmgrd and the demo vendor daemon. 7. Run lmflex and try to check out f3. Observe that the checkout failed because you changed a FEATURE line in a license file and did not regenerate its license signature. Re-signing the License File In the last section, you saw that it is not possible to simply edit the license file, as an end user may try to do, to create a FEATURE line for f3. Now, generate a license file with valid FEATURE lines for both f1 and f3 with lmcrypt. 1. In the platform directory, type lmcrypt counted.lic. The license file should now resemble: SERVER this_host ANY VENDOR demo FEATURE f1 demo 1.0 permanent 4 SIGN="AADD B062 54D1 47E3 \ 1FF6 145F 59CE FE69 0FBC 0000 AA10 FFB3 6EB3" FEATURE f3 demo 1.0 permanent 4 SIGN="CDFE \ AD DEFE 8FDD 0000 ADDE FFB3 3545" 2. Force the license server system to reread the license file by typing lmreread -c counted.lic. 3. Run lmflex again and try to check out f3. Now that you have a valid license for f3, you are able to check out a license for it. 4. When you are finished experimenting, stop the license server system. In the platform directory, type lmdown -c counted.lic. You see a description of the license server system and a request for confirmation: Port@Host Vendors 1) 27000@myhost demo Are you sure (y/n)? 5. Confirm that you want to shut down the demo license server system by typing y, and then exit lmflex. A Locked, Uncounted License This section takes you through the process of locking a license to a specific machine simply by regenerating the FEATURE line within the license file, which incorporates the HOSTID into the license signature. There is no need to modify either the Licensing toolkit or application to incorporate this license policy. The steps below demonstrate how to node-lock the license for feature f2 to your specific machine. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 41

42 Chapter 3: Evaluating FLEXnet Publisher Licensing Toolkit on UNIX Evaluating the Vendor Experience Creating a Locked, Uncounted License Task To retrieve the hostid for your machine and use it to create a license: 1. Use the FLEXnet Publisher Licensing Toolkit command line utility, lmhostid, and type lmhostid at a command-line prompt. It displays the default hostid for your machine. The output looks something like: lmhostid - Copyright (c) by Macrovision Corporation. All rights reserved. The FLEXnet Licensing host ID of this machine is "808386e6" 2. You write over install_dir/platform/uncounted.lic during this sequence, so copy it to a file called uncounted_lic.orig. 3. In the platform directory, open uncounted.lic in a text editor. 4. Locate the FEATURE line for feature f2 and replace the current hostid, ANY, with the value of your machine s hostid. The feature line now looks something like the output shown below: FEATURE f2 demo permanent uncounted HOSTID=80836e6 SIGN="A1C6...52A3" 5. Resign the license file to incorporate the new hostid into the license signature by typing lmcrypt uncounted.lic. Testing the License Run lmflex and try to check out feature f2. A license for feature f2 is successfully granted because the application is executing on the machine to which the license is locked. Exit lmflex, this checks in the license for feature f2. Because the license file for f2 is in the same directory as lmflex and has an extension of.lic, its license is found and used. Additionally, the license for f2 is uncounted; it does not need a license server system to allow it to run. Security Considerations As previously mentioned, the hostid value is incorporated in the license signature and is used in license authentication. Any changes to the license signature, the license HOSTID= value, or the actual machine hostid invalidates the license; the FLEXenabled application fails to authenticate the license and any license requests fail. To demonstrate this concept, try the following: 1. In the platform directory, open uncounted.lic in a text editor. 2. Locate the FEATURE line for feature f2 and modify the value of the HOSTID= keyword to a bogus value, simulating an unauthorized attempt to rehost the license. The feature line now looks something like the output below: FEATURE f2 demo permanent uncounted HOSTID= SIGN="A1C6...52A3" Do not re-sign the license. 42 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

43 Chapter 3: Evaluating FLEXnet Publisher Licensing Toolkit on UNIX Evaluating the Vendor Experience 3. Run lmflex and try to check out feature f2. The license request is denied because the application detects the inconsistency between the HOSTID= value in the feature line and that of the actual machine used to create the signature. The following error messages are displayed: Checkout failed: Invalid host The hostid of this system does not match the hostid specified in the license file Feature: f2 Hostid: a144 License FLEXnet Licensing error: -9,57. System Error: 146 "Connection refused" For further information, refer to the FLEXnet Licensing End User Guide, available at " This last sequence demonstrates FLEXnet Licensing s policy in the license technology. You, the vendor, define the policy which in this case is locked to a specific machine and create the license. You are in control of the license usage until you change it. An Expiring License This section demonstrates an expiring license policy. To implement it, simply set an expiration date in the FEATURE line; there is no need to modify either the Licensing toolkit or application. Then, when the license is signed, the expiration date is incorporated into the license signature. In the steps below, you modify the expiration date to the locked feature f4. The expiration date is included in the license signature and is used in license authentication. Simply moving the expiration date forward will not create a legitimate license; the FLEXenabled application will fail to authenticate the license and any license requests fail. Follow the procedure below to demonstrate this concept. Task To demonstrate an expiring license policy: 1. Run lmflex and try to get a license for feature f4. The license request is denied because the license has expired. 2. You write over expired.lic during this sequence, so copy it to a file called expired_lic.orig. 3. Open expired.lic in a text editor. 4. Locate the FEATURE line for feature f4 and modify the expiration date to a date in the future. The feature line now looks something like: FEATURE f4 demo dec-2010 uncounted HOSTID=ANY SIGN="A1C6...52A3" 5. Save and close expired.lic. Do not resign the license. 6. Run lmflex and try to check out feature f4. The license request is denied this time because the application detects the expiration date has been tampered. The following error messages are displayed: Checkout failed: Invalid (inconsistent) license key The license-key and data for the feature do not match. This usually happens when a license file has been altered Feature: f4 License FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 43

44 Chapter 3: Evaluating FLEXnet Publisher Licensing Toolkit on UNIX Evaluating the Vendor Experience expired.lic:uncounted.lic FLEXnet Licensing error: -8,523. System Error: 146 "Connection refused" For further information, refer to the FLEXnet Licensing End User Guide, available at " 7. Now, re-sign the license file to incorporate the new hostid into the license signature by typing lmcrypt expired.lic. 8. Run lmflex and try to check out feature f4. A license for feature f4 is successfully granted because the license has not expired. Because the license file for f4 is in the same directory as lmflex and has an extension of.lic, its license is found and used. Additionally, the license for f4 is uncounted; it does not need a license server system to allow it to run. 9. Exit lmflex, which checks in the license for feature f4. Building the FLEXnet Publisher Licensing Toolkit In this section, you rebuild the Licensing toolkit to change the strength of tamper-resistant licenses (TRL) authentication from 113 bits to 163 bits. TRL uses public-key technology from Certicom to make the signatures on FEATURE/INCREMENT lines more difficult to counterfeit. As shipped, the Licensing toolkit is shipped with TRL enabled at the 113-bit strength, denoting a public-key length of 113 bits. First, take a look at the FEATURE lines in install_dir/platform/counted.lic, for instance, the line for feature f1. They resemble: FEATURE f1 demo 1.0 permanent 4 SIGN="003D B054 54D1 47E3 1FF6 \ 145F 59CE FE69 0FBC F4FF AA10 EEB3 6EB3" Observe the length of the signature value for the SIGN= keyword. Configuring the FLEXnet Publisher Licensing Toolkit Up until now, you used the prebuilt Licensing toolkit components for this evaluation. As shipped, the Licensing toolkit is in an unconfigured state. You must configure it in order to rebuild it. You use your demo vendor keys provided to you by Macrovision for the following configuration procedure. 1. Change directories to the machind folder. 2. Open lm_code.h in a text editor. Find lines similar to the output shown below: #define VENDOR_KEY1 0x0 #define VENDOR_KEY2 0x0 #define VENDOR_KEY3 0x0 #define VENDOR_KEY4 0x0 #define VENDOR_KEY5 0x0 3. Replace all five lines with the demo vendor key lines that you received from Macrovision. If your demo vendor keys have expired, contact your salesperson at Macrovision. 4. Keep lm_code.h open. 44 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

45 Chapter 3: Evaluating FLEXnet Publisher Licensing Toolkit on UNIX Conclusion Changing TRL Strength 1. In lm_code.h, find the definition of LM_STRENGTH that looks similar to this output: #define LM_STRENGTH LM_STRENGTH_113BIT 2. Redefine LM_STRENGTH to specify 163-bit strength. The definition should look like this output: #define LM_STRENGTH LM_STRENGTH_163BIT 3. Leave TRL_KEYs set to 0x0. They do not get set when using demo vendor keys. 4. Save and close lm_code.h. Building the FLEXnet Publisher Licensing Toolkit For your changes to take effect, you need to build the FLEXnet Publisher Licensing Toolkit. To build your Licensing toolkit, in a command window, change to the platform folder and type make. Make sure the license server system is stopped before you attempt to rebuild the Licensing toolkit. You now have a demo Licensing toolkit that supports TRL at the 163-bit strength level. Since this modification changes the authentication method, all components, including the sample application, lmflex, have been rebuilt. Re-signing the Sample License File Now, regenerate the license file to create license signatures that support TRL authentication at the 163- bit level. 1. Copy counted_lic.orig into counted.lic. 2. In the platform directory, type lmcrypt counted.lic. 3. Open counted.lic in a text editor and look at the FEATURE line for feature f1. You see something like this output: FEATURE f1 demo 1.0 permanent 4 SIGN="01C D AE6C 92CB 0360 \ 1124 AC73 B79B 1785 C C EAAF DF 0FAF 786A \ AA19 E123 52A3" 4. Observe the length of the signature and compare it to the line before you started. 5. Close counted.lic. Conclusion You have completed the evaluation of FLEXnet Publisher Licensing Toolkit on UNIX. When you are ready to build your Licensing toolkit with your production vendor keys, see Creating a Licensed Product: Setting up and Using the Development and Build Environment. If you want to evaluate FLEXnet Publisher Licensing Toolkit on Windows, see Evaluating FLEXnet Publisher Licensing Toolkit on Windows. Remember to set LM_STRENGTH to an appropriate value before you build your production Licensing toolkit. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 45

46 Chapter 3: Evaluating FLEXnet Publisher Licensing Toolkit on UNIX Conclusion 46 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

47 4 License Models A FLEXnet license model employs a basic license model augmented with one or more license model modifiers. In addition, you frequently license the same product under several license models to best match license terms to the needs of your different types of users. A well-designed license model or set of license models allows you to expand your available market, enhance end-user loyalty, and increase account penetration, resulting in increased revenues and profitability. With FLEXnet Licensing s Policy in the License technology, you implement the license model in the license certificate that is delivered to a specific end-user organization, thereby allowing future changes to license terms without changing the product's source code or binaries. The remainder of this chapter walks you through the following steps to create your license model: Table 4-1: Creating a License Model: Basic Steps Step Step 1 Step 2 Description Select your basic license model. See Basic License Models. Decide on the settings for the required license modifiers as described in Required License Model Modifiers. Step 3 Select optional license model modifiers for your license model from Table 4-3, License Model Modifiers. Keep in mind the license server system requirement for the particular modifier. Step 4 Step 5 Step 6 Decide your need for usage-based licensing by referring to Usage-Based Licensing. Decide your support level for mobile licensing. See Mobile Licensing. Determine your need for a license server system. Refer to Deciding the Need for a License Server System. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 47

48 Chapter 4: License Models Basic License Models Basic License Models Table 4-2 presents the basic FLEXnet license model characteristics. You choose one or more of these and build on them to create a model or combination of models that represent your business strategy.. Table 4-2: Basic License Model Characteristics License Types Uncounted Counted Node-locked Applicability: Common. Usage: Allows for unlimited instances of the product to execute on the licensed machine. Terminology: Sometimes referred to as nodelocked/uncounted or just node-locked. Applicability: Uncommon. Usage: Allows for limited instances of the product to execute on the licensed machine. Terminology: Sometimes referred to as node-locked/ counted. Floating Not defined. Applicability: Common. Usage: Each instance of the product consumes a fixed count, usually one, of licenses. Terminology: Floating, network, non-node-locked, concurrent. Node-locked/Uncounted Models With this model, your product is licensed for unlimited concurrent use on a single computer system. The license file is available locally to the same machine on which the product is installed. This model can be used to effect different product configuration schemes: Single feature A single feature license that enables the entire product. Scaled functionality A single product has several levels of functionality built in; access to each level is controlled by a separately FLEXenabled feature. This also allows a single product to be licensed as a limited functionality lite version, a standard version and a pro version to give greater product depth. Evaluation License Model The node-locked/uncounted model is one way to provide evaluation licensing for your product. It allows your product to be licensed for unlimited use on all systems. The license file is located on the same machine on which the product is installed. Characteristics of an evaluation license may include: Limited product functionality Limited number of uses Expiration date 48 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

49 Chapter 4: License Models License Model Modifiers Node-locked/Counted Models A fixed number of licenses is available concurrently over a network, but the licenses may only be used on a specific list of hosts on that network. You get the specific host names from the end user and put them in the license certificate. These host names contribute to authenticating the license signature. The product may then be used on any computer defined in the license certificate. This model requires a license server system. Floating Models This model represents classic networked, concurrent licensing and is sometimes referred to as nonnode-locked/counted, network, or concurrent licensing. It requires a license server system. Entitlement is issued for a specific number of licenses. Entitlement refers to the rights you give your customer to use your FLEXenabled product. For license file-based licensing the license certificates you give your customer defines their entitlement. For a floating model no more than the number of entitled licenses can be used at any one time on a network. However, there are features available to overcome denial of service if all licenses are in use. See Checkout Failure Behavior for further details. License Model Modifiers This section describes modifiers for the FLEXnet Licensing basic license models. They augment the license models that are described in Basic License Models. Required License Model Modifiers Each license has an expiration date and version. Expiration Date The license expiration date is specified in the certificate either with a specific date or with the keyword, permanent. Specify a date for leased, subscription, or time-limited models; specify permanent for non-expiring licenses. Version A version number defines right-to-use entitlement with versions less or equal to that in the license certificate. This is FLEXnet Licensing s notion of the version and not necessarily the same as the product version. You assign your own meaning to the version number. Some examples include: Product version The license version coincides with your product s version. Entitlement is based on the product s version being less or equal to that specified in the license certificate. The advantage of this model is that you only maintain a single version number. However, the disadvantage is that with each product release with a change in the version number, you may need to reissue the license certificate to your customers. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 49

50 Chapter 4: License Models License Model Modifiers License version The license version is independent from the product s version. The notion of the license version is encoded inside the product binary. Entitlement is based on the product s internal license version being less or equal to that specified in the license certificate. For example, your product release version might be 3.1.2, and the the license version could be 3.0. The different numbers allow your customers to run a later version of the product using an older license certificate. This is the most commonly used model, since it gives you the flexibility to decide whether or not the license certificates containing older version numbers still work with the new release. Date-based version The license version is based on a date. The version of the product binary is encoded using a date-based scheme. Entitlement is based on the product s internal date-based version being less or equal to that specified in the license certificate. Note: Date-based versioning pertains to the product version and specifies which version of the product is entitled to run. This modifier is distinct from license start and expiration date modifiers, which specify a date range within which the entitled version is licensed and allowed to operate. Optional License Model Modifiers One or more of these modifiers can be used in combination with your basic model and the required modifiers to customize it for your particular business model. These modifiers are represented in the FLEXnet Licensing implementation by fields in the license certificate, FLEXnet Licensing attributes set in the product, vendor daemon configuration, or end-user options. Table 4-3 lists the modifiers along with a brief description of each. Table 4-3: License Model Modifiers Modifier License Server System Required Description Capacity yes Dynamically adjust entitlement based on system performance parameters. Duplicate grouping yes Defines rules when duplicate requests from the same user, host or display share one license. Requires a counted license. Sometimes referred to as license sharing. Linger yes The license is held, rather than checked in, by the license server system on behalf of the user after the product exits. For a product that is run over and over again in succession by the same user (for example, a compiler), lingering increases the chances that a license is available for that user. Named hosts yes Limits usage to a vendor-defined number of hosts. The list of distinct host names is defined by the end-user license administrator, via the options file. Named users yes Limits usage to a vendor-defined number of users. The list of distinct user names is defined by the end-user license administrator, via the options file. 50 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

51 Chapter 4: License Models Usage-Based Licensing Table 4-3: License Model Modifiers (cont.) Modifier License Server System Required Description Network segments no Limits usage to hosts on a specific subnet. Overdraft no Specifies a number of additional licenses which your end user will be allowed to use, in addition to the licenses they have purchased. This is useful if you want to allow your customers to not be denied service when in a temporary overdraft state. Package yes Defines a set of products or features to be licensed as a single package. Package suite yes Provides a way for users to share floating licenses among components of a package. Platforms no Allows you to restrict usage to particular hardware platforms. Start date no By default, a license is valid as soon as it is signed. However, if a start date is specified, the license is invalid until the start date. Supersede yes Replaces previously issued license rights. Terminal server support no Allows users to run on Terminal Server Client machines or over Remote Desktop. Timeout yes Causes the license to be returned to the general pool of available licenses if the product is not active for a specified number of seconds. Vendor-defined no Used for vendor-defined entitlement such as token-based. Usage-Based Licensing Usage-based licensing is an implementation strategy for license management and is another modifier that can be applied to your basic license model. It provides you and your end-user with the ability to monitor actual product usage patterns and bill or audit based on this usage data. Contact Macrovision if you want to implement this license model. You may need to obtain additional Macrovision products. The report logging functionality of FLEXnet Publisher Licensing Toolkit is fundamental to this model, and, as such, requires a license server system. FLEXnet Publisher Licensing Toolkit supports several usage-based models; some examples include: Overdraft Pay-per-use High watermark of past use FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 51

52 Chapter 4: License Models Mobile Licensing Mobile Licensing End users often want to use a FLEXenabled product on a machine that does not have a continuous connection to a FLEXnet license server system. These situations include: Working on a laptop Using a computer both at work and at home or off-site Working from several different computers not connected to a license server system FLEXnet Publisher Licensing Toolkit supports several kinds of mobile licensing: Table 4-4: Supported Mobile Licensing Licensing Scenario Node-locked to a laptop Node-locked to a FLEXnet ID dongle Node-locked to a user name Fulfilled from a prepaid license pool Soft-mobile Hard-mobile License rehosting Description If a license is to be used exclusively on one laptop computer, that license can simply be node-locked to a hostid of that computer. The license file would reside on the laptop computer. If a license is to be moved between different machines, it can be nodelocked to a FLEXnet ID dongle that connects to a parallel or USB port. This license can be moved between several machines by installing a copy of the license file on each of those machines and moving the dongle from one machine to another. (Windows, Mac OS, and Linux platforms only) If a license is to be used exclusively by one user on different machines, that license can be node-locked to the user s user name. The license file is copied to the different machines on which the user might work; the user s user name must be identical on each machine. The license is fulfilled from a prepaid number of license-days for the usage period. This model is like pay-per-use because each fulfillment is made from a decreasing number of license-days. It is different than other pay-per-use models because, once node-locked to a machine, that machine is allowed unlimited use of the product until the license expires. Licenses are temporarily transferred to a license server system on the mobile laptop. The FLEXenabled product uses an encrypted local file, placed there by the license server system, to do checkouts during the usage period. Mobile license usage is controlled by a FLEXnet ID dongle. If the dongle is attached to a license server system, then the use floats on the network. To temporarily transfer the license, the user moves the dongle from the server to a standalone machine; this removes a license from the served pool until the dongle is replaced on the license server system. This is the consequence of an end user wanting to move a license without using one of the other mobile licensing methods. This means you need to generate a new node-locked license certificate for each new machine. The user is trusted to destroy the previous licenses so that only one is in force at any given time. 52 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

53 Chapter 4: License Models Deciding the Need for a License Server System Deciding the Need for a License Server System You need to decide if your FLEXnet Licensing policy requires a license server system. The need for a license server system stems from either a FLEXnet Publisher Licensing Toolkit requirement, your requirement, your end-user s requirement, or a combination of the three. The term license server system refers to a set of processes, not the machine on which they run. Licenses controlled by a license model requiring a license server system are referred to as served licenses and those not requiring a license server system, unserved licenses. A license server system keeps track of the number of licenses being used for counted models as well as a number of other parameters for both counted and uncounted models. If your licensing policy or deployment requirements have any of the following characteristics, you need to include a license server system in your implementation. A license model that requires a license server system as so noted in Node-locked/Counted Models, Floating Models, and Optional License Model Modifiers A need by you or your end user to capture debug output, which is useful for the end-user license administrator when setting up the system A need by you or your end user to capture license usage activity for analysis by Macrovision products. A need by your end user to centralize licenses for availability over a network A need by the end user to enable end-user options. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 53

54 Chapter 4: License Models Deciding the Need for a License Server System 54 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

55 5 Vendor Decisions This chapter presents licensing policy concepts that you need to think about when designing a licensing policy for your product. Summary of Vendor Decisions Licensing policy decisions fall into two groups: core and license server system. The core decisions define the fundamental behavior of your licensing policy and apply to both served and unserved license models. The license server system decisions apply only to served license models; consider them only if you are implementing a license model which requires a license server system. Consider these decisions after you have decided on the license model. License Models defines license models and guides you through the model decision process. Core decisions Determining Licensable Product Configurations Hostid Support Checkout Failure Behavior Checkin Considerations Optional Diagnostic Handling License server system decisions Maintaining Consistency with the License Server System License Sharing Checkin Considerations for Served Licenses License Server System Redundancy FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 55

56 Chapter 5: Vendor Decisions Core Decisions Core Decisions The decisions presented in this section need to be considered regardless of the license model. Determining Licensable Product Configurations You can license the entire product or just specific features. By designing a creative licensing policy, the same product binary can have several configuration levels such as lite, standard, and pro configurations of the product. Defining various product configurations, or features, is done at the source code level within the FLEXenabled product via calls to the FLEXnet Publisher Licensing Toolkit client library. FLEXnet Licensing does not otherwise understand features within an executable. Additionally, individual products can be grouped together and licensed as a package, or as a package suite. Packages and package suites are defined in the license certificate rather than in the product. This allows you to change the components of a package until just prior to shipping the license or at any time in the future. Hostid Support A hostid is a means used to uniquely identify a specific system. There are two different contexts in which a hostid is used: A FLEXnet license The license is bound to a hostid and is used to define which end-user hosts are licensed to run your product. A FLEXnet license server system One or more hostids are used to define which machines are authorized to run a license server system that serves licenses to hosts on which the product will run. Each type of platform supports one or more methods of determining its hostid. You need to know which system architectures are supported by your FLEXenabled product and decide which hostid scheme you want to support. Table 5-1 provides a summary overview of some of the trade-offs with different hostid approaches. Table 5-1: Hostid Approaches Approach Pro Con Ethernet (MAC) address Disk volume serial number Reasonably secure Always present Not available on all platforms Insecure Dongle Secure Mobile Customers dislike and carries an additional cost Vendor-defined Ultimate in flexibility Programming required IP address Allows end user easy control Insecure 56 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

57 Chapter 5: Vendor Decisions Core Decisions Table 5-1: Hostid Approaches Approach Pro Con Proprietary notice Minimum burden to implement Can be audited Insecure, especially from those who are never audited Pirating risk Serial number No vendor involvement Only mild deterrent, but may be appropriate in certain circumstances In addition to system-specific hostids, several special FLEXnet Publisher Licensing Toolkit hostids are supported. You need to decide which, if any, of these special hostids you will support. Table 5-2: FLEXnet Publisher Licensing Toolkit Special Hostids Hostid ANY COMPOSITE DEMO DISPLAY HOSTNAME USER Description Does not bind the license or license server system to any system. In the context of a license, allows all systems use of the license; in the context of a license server system, allows all systems to run a license server system. Locks the software to a hashed 12-character hexidecimal value formed by combining the values of one or more simple hostids types, as defined by you. Similar to ANY but for use with unserved license models only. It cannot be used in the context of a license server system. Binds the license to a specific display. On UNIX this is /dev/ ttyxx or the X-Display name. On Windows, it is the system name or, in the case of a terminal server environment, the terminal server client name. Binds the license to a system with a specific host name. Allows only users on that host access to the FLEXenabled product. Binds the license to a specific user name. Allows only that user access to the FLEXenabled product. See documentation for lc_hostid() in the C/C++ Function Reference: this section provides a complete list of supported hostids. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 57

58 Chapter 5: Vendor Decisions Core Decisions Checkout Failure Behavior The fundamental operation which allows a given feature to execute within the FLEXenabled product is to check out a license for the desired feature. This operation either succeeds or fails. The behavior for a successful checkout operation should be well defined within your policy. However, your policy also needs to define the FLEXenabled product behavior in the event of a failed checkout. FLEXnet Publisher Licensing Toolkit provides several ways to handle a failed checkout: Table 5-3: Methods Used After Checkout Failure Method Accept overdraft license usage Allow the product to run in a limited mode Wait for a license to become available Deny service: do not allow the product to run at all Allow the product to run Description Even though no additional licenses exist, allow the checkout as an overdraft to proceed and decide how you want to handle license overusage. Setting up a mechanism to charge the end user for the overdraft is one way to handle the overusage. Cripple the product in some manner that provides very basic features or is time limited. In this case, the product will pend, waiting for a license to be checked into the license pool. The FLEXenabled product exits and control is returned back to the end user. In this scenario, the FLEXenabled product operates as if the checkout succeeded. FLEXnet Publisher Licensing Toolkit also provides a way to determine the reason for checkout failure. This allows you to handle each checkout failure differently, depending on its reason. Checkin Considerations Once a FLEXenabled product exits, all licenses are, by default, automatically checked back in to the license pool. Licenses can be checked in asynchronously from the product exiting. You can control the point at which a license is checked back in to the license pool. Additional checkin considerations as they relate specifically to served licenses are discussed in Checkin Considerations for Served Licenses. Optional Diagnostic Handling FLEXnet Publisher Licensing Toolkit provides an optional mechanism for displaying diagnostic messages to the end user. The messages come in two formats: long and short. When you implement FLEXnet Licensing into your product, you configure the diagnostic format. For Windows products, diagnostics can optionally be displayed in an error dialog box. 58 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

59 Chapter 5: Vendor Decisions License Server System Decisions Both formats of error messages are extracted from the FLEXnet Publisher Licensing Toolkit client libraries into text files to provide for localization. License Server System Decisions Continue with this section if your model requires a license server system (see Deciding the Need for a License Server System). Maintaining Consistency with the License Server System A license server system comprises a license server manager and a vendor daemon. The license server manager handles the initial contact with the FLEXenabled product, passing the connection on to the appropriate vendor daemon. It also starts and restarts the vendor daemon. The purpose of the license server manager is to: Start and maintain all the vendor daemons listed in the VENDOR lines of the license file. Refer product checkout (or other) requests to the correct vendor daemon. There are decisions to be made which define the connection strategy between the vendor daemon and the FLEXenabled product. These decisions are implemented in a customized vendor daemon, the FLEXenabled product, or both. Each FLEXenabled product must establish at least one connection to a license server system. This connection is called a job and is managed by a job handle. In a FLEXnet license server system environment, licenses are granted by vendor daemons. There is one daemon for each vendor who has a FLEXenabled product on the network. The vendor daemon keeps track of how many licenses are checked out, and who has them. If the vendor daemon terminates for any reason, all users lose their licenses (though this does not mean the product suddenly stops running). Users normally regain their licenses automatically when the license server manager restarts the vendor daemon, though the application may exit if the vendor daemon remains unavailable. Connection/Reconnection Strategy Upon daemon failure, the FLEXenabled product can: Retry the connection for a specified number of times. Retry forever to connect. Perform pre-reconnection processing. Perform post-reconnection processing. Perform post processing upon reconnection failure. After a pre-set timeout interval, the vendor daemon reclaims inactive licenses. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 59

60 Chapter 5: Vendor Decisions License Server System Decisions Heartbeat Implementation Strategy The FLEXnet license server system uses TCP/IP to communicate to the FLEXenabled product; it can detect when a client connection is gone and frees the FLEXenabled product s licenses automatically. However, a product needs to communicate regularly with the license server system to detect that the server is still running. This communication is effected via heartbeats. By default, regular heartbeats are automatically initiated once a license is checked out. Heartbeats are exchanged with the license server system at a default interval of 2 minutes.this technique is known as automatic heartbeats. If the license server system is shut down and restarted, the heartbeat automatically checks out the complement of licenses that is currently being used by the product. If your product does not send heartbeats to the license server system, the product does not know that the license server system has been shut down and restarted. The FLEXenabled product does not detect that the license server system is down until the time it takes two heartbeats to be exchanged has passed, because the heartbeat acknowledgement checked for by heartbeats is actually the acknowledgement of the previous heartbeat. If you shut down a license server system, the next heartbeat succeeds, because the acknowledgement processed is of the previous heartbeat. If a heartbeat is not acknowledged by the license server system, the product can decide what action to take: continue, warn or terminate. Deciding how the heartbeats occur and what action takes place when the license server system is not running is an important part of incorporating FLEXnet Licensing in a product. On both Windows and UNIX, automatic heartbeats are recommended and are implemented as a separate thread in the FLEXenabled product. For various reasons, you may choose to implement manual heartbeats instead of automatic ones. Some considerations for implementing them include: The product cannot be multithreaded. The product can be interrupted only at specific times. A product can have critical sections of code that cannot be interrupted. Manual heartbeats provide a way for the product to control when the heartbeat thread executes thereby not perturbing the critical sections. See the License File-based Programming Reference for more details on heartbeats and their manual implementation. License Sharing License requests can be grouped so that multiple requests from the same entity share only one license. Such requests are considered duplicates of one another. This is also referred to as duplicate grouping. Duplicate requests are determined on the basis of user name, host name, display name, a combination of the three, or can be vendor-defined. This is a way to effect site licensing. Duplicate grouping requires a counted license model and a license server system. You need to determine if duplicate grouping is appropriate for your business model and licensing policy. 60 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

61 Chapter 5: Vendor Decisions License Server System Decisions Checkin Considerations for Served Licenses In addition to the Checkin Considerations, the following considerations apply to served licenses: Control whether the TCP/IP connection to the license server manager stays open after all licenses are checked in. Manage the checkins from the vendor daemon by defining checkin callback and filtering routines. License Server System Redundancy FLEXnet Publisher Licensing Toolkit supports two methods of redundancy: Via a license-file list in the LM_LICENSE_FILE environment variable. Via a set of three redundant license server systems. With LM_LICENSE_FILE list redundancy, each one of a group of license server systems serves a subset of the total licenses. The end user sets LM_LICENSE_FILE to a list of license files, where each license file refers to one of the license server systems. The application then tries each server in the list, in order, until it succeeds or gets to the end of the list. With three-server redundancy, if any two of the three license server systems are up and running (two out of three license server systems is referred to as a quorum), the system is functional and serves its total complement of licenses. Internal organization of license jobs within the FLEXenabled product affects the way the end user sets up license server systems and the license files on those servers. For served licenses, all features checked out by a given license job need to be served by the same license server system. This effects the usefulness of license-file lists. You need to decide the organization of license jobs within the product. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 61

62 Chapter 5: Vendor Decisions License Server System Decisions 62 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

63 6 License Security Systems Overview There are several aspects of licensing security to consider. The purpose of this chapter is to present the issues and strategies. Actual implementation details are provided in the License File-based Programming Reference. Licensing security means securely enforcing the licensing policy between you and your end user. End users are grouped into two general categories: honest and dishonest. A useful security implementation ensures the honest end user does not, unknowingly, use extra licenses and the dishonest user can not easily disable your licensing. FLEXnet Publisher Licensing Toolkit provides product licensing security in much the same way as a lock provides security to a door. A license key (key to the lock) is needed to unlock the product (lock). The lock does not completely secure the door: it discourages thieves, but the door can be forced open. Limiting Exposure Generally speaking, additional security comes at the cost of inconvenience (or additional financial cost with dongles). FLEXnet Publisher Licensing Toolkit does not require that all end users lock their product the same way. You can decide to use low security measures in certain countries or for selected important end users, while using more secure methods elsewhere. FLEXnet Licensing s Policy in the License technology allows you to use different security mechanisms for different market segments, while not requiring the development and support of multiple versions of your product. Thus, you control your exposure to security risks as appropriate. From a practical point of view, most people with the intent of pirating your product will never pay you any money for it. Guarding against unintentional overuse and providing moderate licensing barriers have the most impact against software pirating. Trying to make the product secure from the dedicated cracker (who will never be a paying customer) can discourage the honest, but severely inconvenienced, end user from buying your product. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 63

64 Chapter 6: License Security Systems License Signature Encryption Method Server-Side Exposure Introduce safeguards in your licensing policy to protect the license server system from being hacked or replaced with an impostor. In the request/grant process, the FLEXenabled product depends on certain responses from the license server system. A hacked or imposter license server system could falsely provide favorable responses that grants unlimited licenses to your product. Product-Side Exposure Implement safeguards to detect imposter license server systems. Prevent strings used for feature names and other components of your license certificate from appearing as clear text within the product binary. Monitor the license server system status via heartbeats. Ensure license server system isn t being stopped and restarted in an attempt to get extra licenses. Prominently display end-user identifying information when product starts up. License Signature Encryption Method FLEXnet Publisher Licensing Toolkit offers two signature encryption methods: Public/private key digital signature (known as Tamper-Resistant Licenses or TRL) Industry-recognized asymmetric, public/private key digital signature ECDSA algorithm Three different signature lengths Mathematically based public key Proprietary digital signature A proprietary, symmetric, digital signature method 48-bit long signatures See Also License File-based Programming Reference for implementation details on either method. Expiring Licenses You can issue a license certificate which either expires on a certain date or is permanent. Some scenarios where an expiring license certificate is prudent include: Demo licenses that are not tied to a specific host (HOSTID=DEMO or HOSTID=ANY). Since demo licenses do not lock your product to a specific host, specifying an expiration date is a way for you to control the entitlement. 64 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

65 Chapter 6: License Security Systems Date Tampering A license certificate used in potentially high-security-risk environments where you want a higher control on entitlement. Opportunities to manage revenue. Issue an expiring license certificate so that revenue can be recognized each time the certificate is renewed. Expiring license maintenance and overhead is higher than with permanent licenses. The security risk for expiring licenses is low; however, security can be compromised by system date tampering. See Also Date Tampering Date Tampering FLEXnet Licensing performs security checks to prevent users from setting system dates back. In addition, Table 6-1 describes measures you can take to make date setback less attractive: Table 6-1: Security Measures to Protect Against Date Tampering Security Measure Prominently display expiration date Provide an insistent reminder Disable some functionality Description Display the expiration date of the license in a prominent place so that the date-setback detection is more public. If it is an expiring evaluation version, periodically do something annoying perhaps a popup that appears every few minutes that encourages the user to purchase the product. An example is a word processing program that alters saved files so that, when printed, the word EVALUATION is printed in large letters across every page. This allows evaluators full functionality, without reasonable utility. HOSTID Choices Using special hostid types, ANY and DEMO, in your licenses provides security risks to be aware of. They specify the universal host, and as such, do not lock your product to a specific system, thus, allowing your product to run anywhere. For a detailed description of how to choose a hostid type see Chapter 5, Hostid Support discusses the decisions you need to make with regard to choosing a hostid type. Table 5-1 gives a comparison of different hostid types and their relative levels of security. Building the Product: Dynamic vs. Static Linking Use a statically linked model whenever possible for linking the FLEXnet Publisher Licensing Toolkit client library into your product. Dynamically linking the Licensing toolkit client library is insecure for the following reasons: FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 65

66 Chapter 6: License Security Systems Tracking End-User Usage It leaves the product vulnerable to being spoofed. The Licensing toolkit dll could be replaced with an imposter. A hacker product can listen to messages transmitted between the product and the dll, thereby gaining intelligence about the licensing policy. To minimize the risk of a dynamically linked model being hacked, make your own DLL that implements Licensing toolkit client wrapper functions. Your product then calls your wrapper functions instead of the Licensing toolkit client functions. This technique provides another layer of security; the hacker would have to compromise your proprietary layer. See the C/C++ Function Reference for more information on dynamically linking your product. Tracking End-User Usage A FLEXnet license server system can produce report logs that are files containing feature usage information. Report log file data can be used for billing, auditing, and market intelligence. Usage data in report log files is encrypted and, as such, provides a relatively secure method of tracking end-user usage. Contact Macrovision for information about products that process the report logs. Usage Data Limitations The report log file, while ASCII (so it can be easily ed), is not human-readable. Vulnerabilities that must be considered include: The end user may simply lose a report log file (either by accident or on purpose). Periods of usage data can be lost without detecting a file modification, although the fact that a time period is missing can be detected. Consider implementing a policy for missing reporting periods. One example policy is: More than x hours per month of missing license usage entries terminates the licensing contract. A similar policy is needed for files that have been altered. 66 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

67 7 License Fulfillment In addition to your licensing policy, you need to decide on methods for license fulfillment and installation at the end-user site. This section covers these topics. License Fulfillment License fulfillment is the process of distributing a license certificate to an end user. Several means exist for accomplishing this task: Via the Internet, also known as automated fulfillment Via Other methods such as via hard copy or verbally Subsections below describe each of these methods. You need to develop a license fulfillment strategy that is compatible with your business model. Back-office management products, such as Macrovision s FLEXnet Operations System, provide you with the capability to support a wide range of functionality within your licensing policy and to manage all the information pertaining to customers and their licenses. FLEXnet Operations permits the distribution of the license certificate by various means. Automated Fulfillment One of the most effective ways for you to distribute and for end users to receive a license certificate is via the Internet. Your end users can gain access to licenses 24 hours a day, seven days a week. Some aspects of automated fulfillment include: Fulfill orders by dynamically building electronic licenses as end user orders are received. These orders may come through online ordering systems, through manual order entry, or with registration cards. Translate product part numbers into electronic licenses based upon product definitions and descriptions of licenses. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 67

68 Chapter 7: License Fulfillment Strategy for Delivering Rights Over Time Manage the phased delivery of licenses so volume orders may be distributed and tracked as the end user takes delivery of licenses. Manage an accurate database of the licenses that have been distributed to specific customers. The license certificate can be delivered via an message, either as an attachment or in the body of the message. FLEXnet Licensing automatically ignores headers and extraneous text when processing the certificate, making it convenient to save the entire message without having to strip out just the license certificate. Other Methods It may be necessary to deliver the certificate by other methods, either because electronic means are not available to your end user or as a backup to your primary electronic means. Other methods include, but not limited to: Mailing a hard copy Faxing a hard copy Verbally relaying the license certificate Strategy for Delivering Rights Over Time Upgrading The initial license certificate distributed to the end user can subsequently be augmented in order to keep pace with changing requirements and usage patterns. With FLEXnet Licensing s Policy in the License technology, there is usually no need to reissue the product binary. For in-depth information on the following types of certificates, see the License File-based Programming Reference. The license certificate provides entitlement for any license version of the product, up to and including the version specified in the certificate. A new UPGRADE certificate can be issued that enables entitlement to a later version of your product. Then, your end user is all set for migrating to the newer version of the product at any convenient time. Incrementing The number of licenses specified in an existing license certificate can be increased. A new INCREMENT certificate can be issued that supplies the end user with additional licenses. 68 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

69 Chapter 7: License Fulfillment Transferring Rights - License Rehosting Superseding You can discontinue use of an older product by distributing a new SUPERSEDE certificate for the new product. A SUPERSEDE license certificate disables the old product licenses and, at the same time, provides licenses for the new product. Support Entitlement Your electronic license certificate, issued at the time of the product transaction, can include a vendordefined support-through date. You can enable your customers to automatically download updates and upgrade their product through the initial support-through date. When they renew support, issue a new electronic license certificate, with a one-year (or 30 day or whatever your policy may be) extension to the support-through date. Transferring Rights - License Rehosting It is common for a end user to want a valid license certificate reissued in order to lock the product, license server system, or both (as applicable to the license model) to a different machine. This process is called license rehosting. There is no mechanism in FLEXnet Publisher Licensing Toolkit to prevent the original license from working after the license has been rehosted. In the license agreement with your end user, it is recommended that you state constraints related to license rehosting. Consider the following: Issue annually expiring licenses to help minimize the impact of additional use from undiscarded license files. Limit the number of free hostid changes you make for an end user. Charge a fee for rehosting. Require a hardcopy from the end-user s site of the rehosting request approved by a corporate financial officer. This way, the request gains visibility within the end-user organization and possibly dissuades convenience rehosting requests. Evaluation Licensing Strategy There are many popular methods of handling evaluation licensing; this section discusses the most common. All models employ HOSTID=DEMO in the license certificate, enabling the product to run on any host without the need of a license server system. FLEXnet Licensing s evaluation license models allow you to conveniently distribute your product for evaluation and, at the same time, control entitlement, because: No license server system is required. License installation is easy. License files are easy to distribute, since no end-user information is required. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 69

70 Chapter 7: License Fulfillment Evaluation Licensing Strategy Limited Time Demos With this model, a fully functional version of your product is available, but for a limited time. The policy is solely contained within the license certificate. Advantage No special coding is required in the product. Disadvantage Vulnerable to system date tampering, which can give unauthorized usage beyond the preset demo period. See Also Date Tampering Limited Functionality Demos Provide your product with limited functionality or with full functionality which is crippled in some way. Provide a license certificate with HOSTID=DEMO. Then, instrument your product to execute with the limited functionality when it detects this hostid. Advantage Risk is low for unauthorized usage, provided the limited function implementation is obfuscated against hacking. Disadvantage Special coding is required in the product. 70 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

71 8 Case Study This chapter presents a case study based on products and business strategies from the fictitious corporation, Widget Design Company. It assumes a basic familiarity with the material presented in previous chapters of this document. Cross references are provided, directing you elsewhere in this document to background material that supports the individual concepts of this case study. Background Widget Design Company has discovered there is a growing problem with uncontrolled use of their flagship product, Widget Design Engine. There is honest overusage as well as unauthorized copies in distribution. Additionally, each product configuration is currently delivered as a separate binary on its own CD. These problems show themselves in loss of potential revenue. To help improve the bottom line, they decide to: Use software licensing to better control and track product usage. Cut production and inventory costs by delivering all product configurations as a single binary on one CD. FLEXnet Publisher Licensing Toolkit Use Case This vendor decides to incorporate FLEXnet license management into their software. FLEXnet Licensing provides them with the usage control they need as well as enabling them to provide a finer granularity of product configurations within a single binary. An additional saving is a reduction in CD manufacturing costs. After carrying out a FLEXnet Publisher Licensing Toolkit evaluation, Widget Design has defined the following licensing policy objectives: Feature-based licensing Single binary for all implementations FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 71

72 Chapter 8: Case Study FLEXnet Publisher Licensing Toolkit Use Case Evaluation, node-locked, and floating license models as appropriate Time-limited licenses subscriptions Free distribution of evaluation version, with limited functionality and time-limited use Until experience has been gained in using electronic licensing, no support at this time for: Mobile licensing or lingering Redundant servers Packages or package suites The Widget Design Engine product consists of a design engine that works with a proprietary data format, editor, advanced editor, and features to import and export data between proprietary and standard formats. Table 8-1 summarizes the features. Table 8-1: Widget Design Engine Feature Matrix Product Configuration Levels Feature Evaluation Standard Advanced Widget Design Engine X X X Editor X X Advanced Editor X Import X X X Export X X 72 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

73 Chapter 8: Case Study License Policy Definition There are three configuration levels for this product: Table 8-2: Licensing Configuration Levels Product Configuration Level Evaluation Standard Advanced Description Available for any machine for a four-week time period. The evaluation configuration provides a limited set of features for the end user to get an idea of the design capabilities of the product. It is crippled (no export capability) so as to provide limited functionally and to persuade purchase of the standard or advanced versions. Available with node-locked or floating licenses. This is a fully functional product that includes the standard editor and allows both import and export. Available with node-locked or floating licenses. This is a fully functional product that includes the advanced editor and allows both import and export. License Policy Definition Based on Widget Design s business model and product structure, their policy design committee formulates the licensing policy. Their decisions are presented below. Basic License Model This vendor has identified two distinct end-user profiles and plans to incorporate this knowledge into their sales model. Thus, they have decided to support both node-locked/uncounted and floating models. See Also Basic License Models License Model Modifiers Required Modifiers Start Date An explicit start date is specified in the license certificate to support their subscriptions. Expiration Date An explicit expiration date is specified in the license certificate to support their subscriptions. Version An independent license version scheme, apart from the product version, is implemented. Optional Modifiers Vendor-defined string is used to specify the end-user organization name. Supersede is used to support upgrading from the standard configuration to professional. See Also Required License Model Modifiers Optional License Model Modifiers FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 73

74 Chapter 8: Case Study License Policy Definition Usage-Based Licensing No formal usage-based licensing is implemented at this time. See Also Usage-Based Licensing Mobile Licensing No mobile licensing strategies are implemented at this time. See Also Mobile Licensing License Server System Requirement Widget Design plans to include a floating license model in their licensing policy offering. Additionally, there could be a future need to track license usage activity. For these objectives, a license server system is required. See Also Deciding the Need for a License Server System Vendor Decisions When implementing FLEXnet Licensing, the vendor needs to make several decisions regarding product configurations, hostids, checkin and checkout behavior, and the license server system. Licensable Product Configurations Table 8-1 defines the product configurations and corresponding configuration feature names. The product configurations are referred to by the following names within the binary and license certificate: Table 8-3: Licensing Feature Names Product Configuration Level Evaluation Standard Advanced Licensing Feature Name eval standard pro See Also Determining Licensable Product Configurations 74 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

75 Chapter 8: Case Study License Policy Definition Hostid Support The ethernet address is the architecture hostid type of choice for each of the three supported platforms: Windows, Solaris, and Linux. In addition, the special hostid type, DEMO, is supported for the evaluation configuration. See Also Hostid Support Checkout Failure Behavior For checkout failures with the standard or advanced product configurations, Widget Design is allowing the product to run, but at the evaluation level. Additionally a message, indicating the checkout failure, is displayed to the user. Checkout failures with the evaluation configuration denote the license has expired and usage is denied. A warning message to this effect is displayed to the user with remedial suggestions. See Also Checkout Failure Behavior Checkin Considerations All licenses remain checked out for the duration of product execution. They get checked in and returned to the general pool upon product exit. There are no vendor daemon callback or filtering routines; all checkins are handled in a simple manner. See Also Checkin Considerations Checkin Considerations for Served Licenses License Server System Consistency Widget Design has decided to use the default license server system reconnection and heartbeat strategies: The default operation of the FLEXenabled product when the connection to the license server system is lost is to try five times to reconnect and then exit the product. Regular heartbeats are automatically initiated once a license is checked out. Heartbeats are exchanged with the license server system at a default interval of 2 minutes. See Also Maintaining Consistency with the License Server System License Sharing License sharing is not implemented. See Also License Sharing FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 75

76 Chapter 8: Case Study License Policy Definition Licensing Security A major objective for Widget Design is to gain control over unauthorized product usage and thereby increase revenues. They feel FLEXnet license management gives them most of the security they need against the piracy issue stated in Background. Considering their marketplace and usage patterns, they are employing a few more security measures: Use Tamper-Resistant Licenses (TRL) signature encryption. See License Signature Encryption Method. Prominently display information that identifies the end-user organization when the product starts up. See Limiting Exposure. Issue expiring licenses, which effectively implements product subscriptions that are renewed on a regular basis. See Expiring Licenses. For the Windows platform, implement a static-linked product build model. See Building the Product: Dynamic vs. Static Linking. Use the special hostid type, DEMO, with the evaluation product configuration. See HOSTID Choices. License Fulfillment Widget Design supports license certificate fulfillment via and, with the FLEXnet Operations Automated Fulfillment option, the Internet. See Also License Fulfillment Usage Rights over Time Entitlement is controlled via the expiration date in the license certificate and license version in the product. End users are allowed to download new product versions and corresponding license certificates within their subscription period. See Also Strategy for Delivering Rights Over Time License Rehosting License rehosting is supported through Widget Design s Help Desk. See Also Transferring Rights - License Rehosting Evaluation Licensing Strategy The licenses for the evaluation product configuration are both time and functionally limited. Providing time-limited license certificates increases the chance that the end user will stay in contact with Widget Design and someday purchase a fully functional product. 76 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

77 Chapter 8: Case Study Sample License Certificates See Also Limited Time Demos Limited Functionality Demos License File Location The product specifies the location where it expects to find the license certificate. For ease of coexisting with other vendors FLEXenabled products, the end user can override this by setting the LM_LICENSE_FILE environment variable. Sample License Certificates Taking into consideration all of the license model decisions Widget Design has made, this section presents representative examples of license certificates for each one of their license models. Evaluation Product Configuration Certificate The following license certificate is for the evaluation configuration of Widget Design Engine: FEATURE eval widget jan-2009 uncounted HOSTID=DEMO VENDOR_STRING=end_user_org SIGN=signature The following table describes the items in this license certificate. Table 8-4: Evaluation Product License Certificate Descriptions Certificate Element eval widget Description The feature name. Specifies the evaluation product configuration. The vendor daemon name. 2.0 Specifies entitlement up to and including v2.0 of the product. 1-jan-2009 uncounted HOSTID=DEMO end_user_org signature Specifies license certificate expiration date. Specifies entitlement for unlimited number of licenses. Specifies entitlement for any host. Specifies the end-user organization identifier. This information is displayed at product startup. Specifies the authenticated signature based on all previous fields in the certificate. Since this license certificate is uncounted, it does not require a license server system. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 77

78 Chapter 8: Case Study Sample License Certificates Standard Product Configuration Certificate Floating License SERVER lulu 17007ea8 VENDOR widget FEATURE standard widget nov START=1-nov-2006 \ VENDOR_STRING=end_user_org SIGN=signature The following table describes the items in this license certificate. Table 8-5: Standard Product License Certificate for Floating Licenses Certificate Element lulu 17007ea8 standard widget Description Specifies the license server system to which the certificate is locked. The feature name. Specifies the standard product configuration. The vendor daemon name. This appears in two places: the VENDOR line and the FEATURE line. 2.0 Specifies entitlement up to and including version 2.0 of the product. 1-nov-2009 Specifies license certificate expiration date. 5 Specifies entitlement for five concurrent licenses. START=1-nov-2006 end_user_org signature Specifies the date on which entitlement starts. The license is disabled before this date. Specifies the end-user organization identifier. This information is displayed at product startup. Specifies the authenticated signature based on all previous fields in the certificate. Node-locked License FEATURE standard widget nov-2009 uncounted \ START=1-nov-2006 HOSTID=ethernet_addr \ VENDOR_STRING=end_user_org SIGN=signature The following table describes the items in this license certificate. Table 8-6: Standard Product License Certificate for Node-Locked Licenses standard widget The feature name. Specifies the standard product configuration. The vendor daemon name. 2.0 Specifies entitlement up to and including version 2.0 of the product. 1-nov-2009 Specifies license certificate expiration date. 78 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

79 Chapter 8: Case Study Product Deliverables Table 8-6: Standard Product License Certificate for Node-Locked Licenses uncounted START=1-nov-2006 ethernet_addr end_user_org signature Specifies entitlement for unlimited number of licenses. Specifies the date on which entitlement starts. The license is disabled before this date. Specifies the ethernet address of the machine to which the license is locked. Specifies the end-user organization identifier. This information is displayed at product startup. Specifies the authenticated signature based on all previous fields in the certificate. Similarly, license certificates for the professional configuration specify pro as the feature name. Updating the License Certificate When Widget Design upgrades their software from version 2.0 to version 3.0, they issue a new license certificate that upgrades the end user s older certificate. The certificate, which is shown below, disables the original five floating licenses for the standard product configuration and replaces them with five new ones good for software versions up to and including version 3.0 within the same subscription period (expiration date is still 1-nov-2009). UPGRADE standard widget nov START=1-nov-2006 SIGN=signature An end user may decide to move from the standard configuration to the professional one. To support this change, Widget Design would issue a superseding license certificate disabling the standard configuration licenses and activating the professional configuration. The following is an example: FEATURE pro widget nov START=1-nov-2006\ SUPERSEDE="standard" HOSTID=ethernet_addr SIGN=signature The above certificate is appended to the original license certificate and is valid throughout the same subscription period (expiration date is still 1-nov-2009). Issuing the certificate without SUPERSEDE would allow five licenses for both the standard and professional configurations. Product Deliverables Widget Design ships various components with the FLEXenabled product to the end users. This list of components includes: FLEXenabled vendor application binary License Administration Guide either verbatim or customized FLEXnet Publisher Licensing Toolkit utilities; for Windows platforms, LMTOOLS License certificate FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 79

80 Chapter 8: Case Study Product Deliverables A list of implementation decisions, as appropriate Additionally, Widget Design ships the following components as required: The license server manager lmgrd The vendor daemon 80 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

81 Glossary Term activation specification record (ASR) activatable license activation Meaning A signed XML file used with local activation and short code activation that contains information about license rights, configuration settings for the publisher s trusted storage segment, and additional information required by the activation transaction. A license right in trusted storage that can be activated to a FLEXenabled client. See also license group. In FLEXnet Publisher Licensing Toolkit, this is a process used to load license rights into trusted storage. Different activation types include: programmatic activation manual activation short code activation local activation In FLEXnet Operations, this is a process used to generate license rights in either trusted storage and in license files. activated feature line Activation API activation client See feature definition line. Functions available in the FLEXnet Publisher Licensing Toolkit libraries that allow you to initiate transactions and manage license rights in trusted storage. The Activation API is used to develop the functionality in an activation utility. The system that works with an activation server to receive license rights. This system can be either a license server or a FLEXenabled client. The activation client initiates an activation, repair, or return transaction with an activation server, using an activation utility. The following transaction types can be initiated by an activation client: activation transaction return transaction repair transaction FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 81

82 Glossary Term activation request activation response activation server Meaning A message sent by an activation utility to an activation server that initiates an activation transaction. A message sent from an activation server to an activation client, in response to an activation request. This message defines the license rights. A system that responds to requests for license rights from an activation client. The activation server can be one of the following: a license server FLEXnet Operations an LGT-based activation server An activation server can also perform repair and return transactions. activation transaction activation utility A sequence of activation request and activation response messages, and related actions that result in license rights being loaded into trusted storage. A utility that initiates an activation transaction, repair transaction, or return transaction by sending a request to an activation server. This utility also processes the response received from the activation server. It uses the Activation API to perform these capabilities. It is written by the software publisher to meet specific business process requirements. This application can be either separate from or embedded in the FLEXenabled application. anchor ASR file binding borrowing bulk entitlement checkin checkout client system A link between the system and the trusted storage that is used to detect whether trusted storage has been tampered with, deleted, or restored. Anchors are also used to ensure that information in trusted storage about trial licenses persists beyond the expiration date. See activation specification record (ASR). A capability used with trusted storage where one or more properties of a system, combined together into a unique identifier, are used to ensure that license rights held in trusted storage are not copied to another system. A capability available in FLEXenabled applications that enables a user to temporarily obtain a license in such a way that the license can be used locally for a limited period of time while the user is disconnected from the local network. An entitlement created for an order of multiple copies of a single product or suite. Bulk entitlements are used for sales through reseller channels. The transaction that a FLEXenabled application performs to return a license after it has been checked out. This operation is not the same as an activation transaction. FLEXenabled applications must perform a checkout and checkin transaction to use a license. The transaction that a FLEXenabled application performs to request a license. This transaction is different than activating a license. FLEXenabled applications must perform a checkout and checkin transaction to use a license. A general term used to define any system that interacts with a server in a client-server relationship. When using FLEXnet Publisher Licensing Toolkit there are two types of clients: activation client FLEXenabled client 82 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

83 Glossary Term concurrent license config response consumer counted debug log file demo license duplicate grouping embedded activation encryption seed end-user Meaning A license that can be shared among users by allowing each user to check out and then return the license. These licenses are served to FLEXenabled applications from a license server. If all licenses are being used, an additional user cannot run the FLEXenabled application until one of the other users check in their license. When one user finishes using the license, another user can begin using it. Also called floating license or served license rights. A response to any request from an activation client that contains information about how the publisher s trusted storage segment must be configured (called the trusted storage segment configuration). This response is processed by the activation utility and results in a segment of trusted storage being created or re-configured for that publisher. An individual or small business who purchases a license for their individual use. Compare with enterprise. A type of license right or license model that defines a multiple quantity of licenses and allows concurrent use of the licenses. This term is taken from the fact that the license server counts the number of licenses that are being used. A file used by the license server to record status and error messages that are useful for debugging the license server. Each license server can have one or more of these files. See trial license. A capability in the FLEXnet Publisher Licensing Toolkit used to uniquely identify a single client (or client checkout request) for the purpose of counting the number of licenses that are used. Duplicate grouping defines a set of rules under which multiple checkout requests can share the same license(s). See local activation. A set of values defined by a software publisher that are used when creating a publisherspecific vendor daemon. A person who uses a FLEXenabled application. This role is not the same as a license administrator. end-user system See client system. end-user license administrator See license administrator. enterprise An organization that purchases licenses on behalf of a number of individual users. Compare with consumer. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 83

84 Glossary Term entitlement Meaning A representation of the license model and product that a customer has bought. It is a definition only. The customer will need to fulfill the entitlement so that the license rights can be populated to license files or trusted storage. In FLEXnet Operations, there are two types of entitlements: bulk entitlement simple entitlement Each entitlement is uniquely identified by an entitlement ID. entitlement ID In FLEXnet Publisher Licensing Toolkit, an attribute in trusted storage that stores a value used to identify the customer s entitlement. In FLEXnet Operations, a value that uniquely identifies the entitlement. expiring license feature License rights granted to a customer for a limited duration. When the license rights have expired, the licenses can no longer be checked out. In the context of a software application, this is a single unit of capability. In FLEXnet Publisher Licensing Toolkit, this is an identifier used to associate a license model to a unit of capability in a software application. The software publisher defines which features in their software application map to a single feature in FLEXnet Publisher Licensing Toolkit. For example, a feature in FLEXnet Publisher Licensing Toolkit could represent any of the following: The entire software application. A subset of menu items. A specific set of data available from the software application. A process in the software application. The software publisher also defines the license model for each FLEXnet Publisher Licensing Toolkit feature. This gives software publishers the ability to define a different license model for each feature in the software application. feature bundle feature definition line A collection of features in FLEXnet Operations. It exists primarily to enable modularity and re-use. An entry in a license file or fulfillment record that describes a feature. Each line begins with the keyword FEATURE, INCREMENT, or UPGRADE. In license files, feature definition lines are used with SERVER and VENDOR lines to define the license model. In trusted storage, feature definition lines are used with the fulfillment record properties to define the license model. feature line file-based activation FLEXenabled application FLEXenabled client See feature definition line. See manual activation. A software application that uses FLEXnet Publisher Licensing Toolkit to implement its license models. A client system where a FLEXenabled application is installed. 84 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

85 Glossary Term FLEXible API FLEXnet Agent FLEXnet Manager FLEXnet Operations floating license fulfill fulfillment record heartbeat hop count hostid hostid type hybrid license internet activation keyboard activation Meaning Functions available in the FLEXnet Publisher Licensing Toolkit libraries that allow FLEXenabled clients to access license rights. A utility that runs on a license server and allows communication between the license server and other FLEXnet products. This is a license server management and license management decision support solution in the FLEXnet product family that allows companies to centrally manage license servers and license usage across the enterprise. A product in the FLEXnet family of products that manages entitlements and generates license rights. A license that can be shared among users and is served to FLEXenabled applications from a license server. When a user finishes using the license, another user can begin using it. Also called concurrent license or served license rights. The action of getting license rights. In FLEXnet Publisher Licensing Toolkit, a data structure specific to trusted storage that defines license rights. A type of message sent periodically between two systems (for example, a FLEXenabled application and a license server) to identify whether each is running and able to communicate with the other. In FLEXnet Publisher Licensing Toolkit, the number of times that license rights in a single fulfillment record have been transferred from one license server to another. In FLEXnet Publisher Licensing Toolkit, the value of a specific system attribute that uniquely identifies the host. For example, if IP address is a hostid type, then the hostid might be Hostids are used in node-locked license. A type of attribute that is available to uniquely identify a system. For example, disk serial number, IP address, or MAC address. In FLEXnet Publisher Licensing Toolkit, a type of license right in the license group on trusted storage that can function as either a concurrent license or as an activatable license. See programmatic activation. See short code activation. license administrator license file license-file list A person in an enterprise who is responsible for installing the FLEXenabled application and administering the licenses and license servers. A text file, usually with the.lic extension, that contains license certificates from one or more publishers. See license search path. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 85

86 Glossary Term license generator Meaning A general term used to describe any mechanism a software publisher uses to generate license rights for their customers. The following FLEXnet capabilities and products can function as a license generator: LGT-based activation server: generates license rights for trusted storage. FLEXnet Operations: generates license rights for trusted storage and license files. lmcrypt: generates license rights for license files. License Generator API (LGAPI) A set of functions in the FLEXnet Publisher License Generator Toolkit (LGT) used to create an activation server. License Generation Toolkit (LGT) A product in the FLEXnet product line used to create an activation server. license group A mechanism used to describe licenses rights held in server-side trusted storage. These groups are not used with license rights held in license files. activatable A license right in trusted storage that can be activated to a FLEXenabled client. concurrent license rights in this group can be shared among users by having a FLEXenabled client to check out, and then return the license. hybrid these license rights have the same characteristics as both the activatable license group and concurrent license group. They can be activated to client-side trusted storage on a FLEXenabled client or checked out by a FLEXenabled client. Although you see these group names used to describe license rights in client-side trusted storage, the capabilities of the license rights do not change. Once license rights are in client-side trusted storage, you cannot transfer, serve, or activate them to another system. The FLEXenabled application can only check out and check in these licenses. The group names are used when a license right is returned to the license server, so that it is assigned to the correct license group on the license server. license model license rights license search path license server The set of characteristics that determine the conditions under which (for example, how, when, where, and by whom) a FLEXenabled application can be used. Information in trusted storage or license files that defines the license model and controls user access to a specific FLEXenabled application. A property that the FLEXenabled application uses to locate where license rights are stored. Sometimes known as a license-file list. A set of files from the FLEXnet Publisher Licensing Toolkit, that work together to manage and serve licenses to FLEXenabled applications. A license server is required to support a concurrent license model. The license server consists of a license server manager, one or more vendor daemons, zero or more options files, zero or more debug logs, and, optionally, a report log. These components are available in the FLEXnet Publisher Licensing Toolkit. If the license server supports license rights held in trusted storage, it also includes an activation utility. It may, optionally, act as an activation server. 86 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

87 Glossary Term license server system Meaning See license server. license server manager (lmgrd) license sharing The lmgrd executable that forwards connections from a FLEXenabled application to the correct vendor daemon. Because the vendor daemons are responsible for authenticating requests and serving licenses, a single license server manager can be used with multiple vendor daemons on the license server. A capability available in FLEXnet Publisher Licensing toolkit where multiple license requests from the same user, host, or display results in only one license being used. Also known as duplicate grouping. licensing client local license rights local activation See FLEXenabled client. License rights that are stored on the same system where the FLEXenabled application is running, rather than on a license server. A type of where license rights are loaded using an ASR file. The ASR file must reside with the FLEXenabled application. This does not require user intervention. machine ID maintenance manual activation A value, generated using attributes of the system, that is used to bind trusted storage to that system. A maintenance represents a customer s right to obtain updates and upgrades to a particular licensed product or suite for a specified duration. Used in FLEXnet Operations. An type of where license rights are transmitted from an activation server to another system using a set of request and response messages that are formatted as XML. These messages are saved to and read from physical XML files. An activation utility loads the license rights from an XML file into trusted storage. node-locked license options file orderable package A license that can be used only when the FLEXenabled application is run on a specific system or by a specific user (as defined by the hostid). A configuration file available on the license server that license administrators can use to either change license server behavior or implement certain licensing policies. Each software publisher has its own separate options file that works with a specific vendor daemon. Anything that can be purchased by a customer. Orderables can include suites, products, documentation, and maintenances. In FLEXnet Publisher Licensing Toolkit, a set of features that can be grouped and licensed together. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 87

88 Glossary Term part number permanent license product product ID programmatic activation Meaning A unique identifier, typically correlated with an order system, assigned by a publisher to a product. License rights granted to a customer that do not expire. Anything that can be sold by a publisher and can be licensed. In FLEXnet Publisher Licensing Toolkit, one of the values that uniquely identifies the license rights in trusted storage. See also entitlement ID. A type of where license rights are transmitted from one system to another across a network using a set of request and response messages that are formatted as XML. This process is the identical to manual activation, except that it does not generate a physical XML file. An activation utility loads the license rights from the XML message into trusted storage. This is an automated process and does not require user intervention. publisher ID quorum rehost repair request repair response repair transaction report log file return request return response return transaction A value used by trusted storage to uniquely identify the software publisher s logical and physical licensing components. Macrovision distributes this identifier to software publishers. It is used to prepare certain FLEXnet Publisher Licensing toolkit files that access trusted storage. This value is not the same as the vendor name. A condition specific to three-server redundancy that is met when at least two of the three license servers are running and can communicate with each other using heartbeats. The process of reissuing a license for a different system. This process requires software publishers to perform certain activities to redefine the license rights so that they will work properly on the new system. A message sent by an activation utility to an activation server that initiates a repair transaction. The activation server provides the information that repairs the license rights in trusted storage. An activation utility is an application that initiates the repair transaction. A message sent from an activation server to an activation client, in response to a repair request. This message contains information that is used to the repair the license rights. A sequence of repair request and repair response messages, and the related actions that result in license rights being repaired in trusted storage. A file that runs on a license server that contains data about the features used by a single vendor daemon. Report logs are encrypted and cannot be read by a person, but are used by FLEXnet Manager to produce reports. A message sent by an activation utility to an activation server that initiates a return transaction. The activation server receives the license rights returned by an activation client. An activation utility is an application that initiates the return transaction. A message sent from an activation server to an activation client, in response to a return request. A sequence of return request and return response messages, and the related actions, that result in license rights being returned from trusted storage to the activation server. 88 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

89 Glossary Term served license rights short code short code activation signature simple entitlement Meaning License rights that are stored on a license server and are checked out when needed by FLEXenabled applications that run on client systems. These license rights are used for concurrent licensing. A multi-character code used with a short code activation transaction, a repair transaction, or a return transaction. A type of activation where license rights are loaded from an ASR file using an activation transaction that requires a specific code (called a short code). Often the user enters this code into a prompt from the application. This is also is used for licensing via automated telephony. A secure multi-character string added to the license certificate that ensures it has not been modified. An entitlement for a single, specific customer. suite supersede three-server redundancy triad A set products grouped together that are functionally complementary and associated with one or more license models. A capability in FLEXnet Publisher Licensing Toolkit, used to replace the characteristics of old license rights with new characteristics. A capability in the FLEXnet Publisher Licensing Toolkit that enables license administrators to configure three license servers in a failover cluster. A set of three license servers which operate together to support three-server redundancy. trial license trusted storage trusted configuration trusted configuration file trusted storage configuration uncounted unserved license rights License rights granted to a user for a limited duration so that the user can evaluate the software application. A tamper-proof area on the system that stores license rights. This storage location is different than license files and requires a different mechanism for loading and managing license rights. Compare with license file. A set of attributes that define the security configuration of a segment of trusted storage. Each software publisher can configure their segments of trusted storage differently. This configuration defines the settings for binding, anchoring, and windback detection. A file that stores the attributes that define a software publisher s trusted storage segment configuration. See trusted configuration. A license right attribute that allows an unlimited number of concurrent uses of a FLEXenabled application. Compare with counted. These are license rights that are not served from a license server. These license rights are located with the FLEXenabled application. Also known as local license rights. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 89

90 Glossary Term upgrade upsell vendor daemon Vendor Certificate Generator vendor name windback windback detection Meaning A process where a user installs a newer version of a FLEXenabled application and also updates the license rights so that they can use this newer version. The process of transitioning from a product of lesser functionality to one of greater functionality in the same product line. One of the files that is a part of the license server. This executable is customized and built by the software publisher using files in the FLEXnet Publisher Licensing toolkit. The vendor daemon is responsible for communicating with the FLEXenabled application and issuing licenses. A publisher-built component, that is a part of FLEXnet Operations, that creates license certificates or signed feature lines in fulfillment records. This functions similarly to lmcrypt. A value used to uniquely identify a software publisher s logical and physical licensing components. It is used to prepare certain files in the FLEXnet Publisher Licensing toolkit that manage license rights in both trusted storage and license files. Macrovision distributes this identifier to software publishers. This value is not the same as the publisher ID. A condition where the system clock has been set to an earlier date or time. One reason users change the system clock is to extend the license duration. A capability in FLEXnet Publisher Licensing Toolkit that detects whether a user has reset the system clock. This prevents a user from extending the duration of the license. windback tolerance An acceptable amount of windback to a system clock that won't trigger windback detection. A certain tolerance is normally allowed to account for time zone differences or Daylight Saving Time. 90 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

91 Index A activatable license 81 activated feature line, See feature definition line activation 81 short code 89 activation API 81 activation application 82 activation client 81 activation request 82 activation response 82 activation server 82 activation specification record 81 activation transaction 82 administration options file, end-user 17 administration, vendor 40 anchor 82 application, FLEXenabled 16 application-side exposure 64 B basic license models 48 behavior checkout failure 58 binding 82 borrowing 82 build.bat 32 building the application, dynamic vs. static linking 65 bulk entitlement 82 C C environment on Windows 31 capacity 50 certificate, license 16 checkin 82 checkin considerations 58 served licenses 61 checkout 82 checkout failure behavior 58 choices, hostid 65 client system 82 component license model 14 overview 16 concurrent license 83 config response 83 configuration, determining licensable product 56 connection/reconnection strategy 59 considerations checkin 58, 61 consistency with the license server system, maintaining 59 Consulting Services 2 consumer 83 Contacting Macrovision 2 core decisions 56 counted license 83 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 91

92 Index D daemon, vendor 17, 90 data limitations, usage 66 date tampering 65 date-based version 50 debug log file 17, 83 decisions core 56 license server system 59 summary of vendor 55 delivering rights over time, strategy for 68 demo license server system overview 37 starting 37 stopping 39 demo license, See trial license demos limited functionality 70 limited time 70 determining licensable product configurations 56 diagnostic handling, optional 58 duplicate grouping 50, 60, 83 E 68 embedded activation, See local activation enabled product, FLEXnet Licensing 16 encryption method, license signature 64 encryption seed 83 end user 83 end-user administration options file 17 end-user license administrator, See license administrator end-user machine, See client system end-user usage, tracking 66 enterprise 83 entitlement 84, 86 entitlement ID 84 entitlement, support 69 evaluation licensing 48 evaluation licensing strategy 69 expiration date 49 expiring license 84 expiring licenses 64 exposure F application-side 64 limiting 63 server-side 64 failure behavior, checkout 58 feature 84 feature bundle 84 feature definition line 81, 84 FEATURE/INCREMENT line, See feature definition line file debug log 17 end-user administration options 17 license 85 options 87 report log 18, 88 file-based activation, See manual activation FLEXenabled application 16, 84 FLEXenabled client 84 FLEXible API 85 FLEXnet Agent 85 FLEXnet license server manager 17 FLEXnet Licensing for Java Programmers Guide 11 FLEXnet Publisher Operations 85 floating 49 floating license 85 fulfill 85 fulfillment license 67 web 67 fulfillment record 85 functionality demos, limited 70 G grouping duplicate license requests 60 H handling, optional diagnostic 58 heartbeats 85 implementation strategy 60 hop count 85 host, named 49 hostid FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

93 Index choices 65 support 56 hostid type 85 hybrid license 85 I implementation strategy, heartbeat 60 incrementing 68 installation, license 67 installing, license certificate 67 internet activation, See programmatic activation Introduction to Licensing-File Based Licensing 13 K keyboard activation, See short code activation Knowledgebase 2 L LGAPI 86 LGT 86 licensable product configurations, determining 56 license checkin considerations for served 61 counted 83 expiring 64 fulfillment 67 installation 67 mobile 52 rehosting 69 served 15, 89 site 60 unserved 14, 89 usage-based 51 version 50 License Administration Guide 11 license administrator 85 license certificate 16 license file 85 rekeying 28, 41 sample License Generation Toolkit 86 license generator 86 License Generator API 86 license group 86 license model 47, 86 basic 48 components 14 modifiers 49 license request process 18 license requests, grouping duplicate 60 license rights 86 local 87 license search path 86 license server 86 license server manager 17, 87 license server manager, definition 87 license server manager, FLEXnet Licensing 17 license server system 87 deciding the need for 53 decisions 59 maintaining consistency with 59 license server system requirements 53 license server system, demo 37 license sharing 87 license signature encryption method 64 license-file list, See license search path licensing client 87 licensing strategy, evaluation 69 licensing, evaluation 48 limitations, usage data 66 limited functionality demos 70 limited time demos 70 limiting exposure 63 linger 50 lmgrd 17 definition 87 local activation 87 local license rights 87 log file debug 17, 83 report 18, 88 M machineid 87 maintaining consistency with the license server system 59 manager, FLEXnet license 17 manual activation 87 methods license signature encryption 64 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 93

94 Index other 68 Microsoft Visual C++, building with 31 mobile licensing 52 model basic license 48 license 47, 86 model components, license 14 model modifiers, license 49 modifiers, license model 49 N named host 17, named user 17, 50 need, license server system 53 network segments 51 newlink GlossaryC 82 node-locked/uncounted 48 O optional diagnostic handling 58 optional license model modifiers 50 options file 87 end-user administration 17 overview 47, 63 component 16 P package 51, 87 package suite 51 part number 88 permanent license 88 product 88 product configuration, determining licensable 56 product version 49 programmatic activation 88 publisher id 88 Q quorum 88 R regular entitlement, See simple entitlement rehost 88 rehosting, license 69 rekeying 28, 41 repair request 88 repair response 88 report log file 18, 88 requests, grouping duplicate license 60 required license model modifiers 49 return request 88 return response 88 return transaction 88 rights over time, strategy for delivering 68 rights, transferring 69 S served license rights 89 served licenses 15 checkin considerations 61 server deciding the need for 53 license 87 license decisions 59 maintaining consistency with the license 59 server-side exposure 64 setting up C environment 31 short code 89 short code activation 89 signature 89 signature encryption method, license 64 simple entitlement 89 site license 60 strategy connection/reconnection 59 delivering rights over time 68 evaluation licensing 69 heartbeat implementation 60 suite 89 summary of vendor decisions 55 supersede 51, 89 superseding 69 support entitlement FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

95 Index T hostid 56 tampering, date 65 Technical Support 2 three-server redundancy 89 time, strategy for delivering rights over 68 timeout 51 tracking end-user usage 66 Training Services 2 transferring rights 69 triad 89 trial license 89 trusted configuration file 89 trusted storage 89 trusted storage configuration 89 type, hostid 85 U uncounted license uncounted 89 unlicensed feature 39 unserved license rights 89 unserved licenses 14, 89 upgrade 90 upgrading 68 upsell 90 usage data limitations 66 usage, tracking end-user 66 usage-based licensing 51 V vendor administration 40 Vendor Certificate Generator 90 vendor daemon 17, 90 vendor decisions, summary 55 vendor name 90 vendor-defined 51 version 49 W web fulfillment 67 windback 90 windback detection 90 windback tolerance 90 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 95

96 Index 96 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing