Simple 'Light Switch' Approach

Customer License Scenario - A Simple 'Light Switch' (ON/OFF)

Customers often just want a simple 'Light Switch' license approach for using your products. Often requesting to not register for use of the software. While Nitro-LM can be configured to support these types of requests, your company will suffer from the the following at minimum:

  • no understanding of who is doing what, when and where.
  • no ability to help customers that are using software over multiple machines and have "ran out" of licenses due to end users "checking-out" licenses from Nitro-LM. (this is a common and frustrating problem)
  • additional workload and support will be required for distribution to support simplified requirements of some customers while trying to maintain the flow of valuable usage data for all of your other customers.

Implementing a 'Light Switch' License Model

Again, these methods are fundamentally risky in that you will not be able to understand important information about your customers in relation to your software. Please consider the customers needs for simplicity relative to your need for information relative to YOUR needs for information to help them and help yourself guide your product features and development path.

Method 1 - Hard Code a Default/Shared User Account

Normally, Nitro-LM requires each user to be registered and confirmed in order to use a license of your software. While this is crucial to the understanding and control of what individual users are doing with your software, you can hard-code a default or shared users account into your software. By doing this, there will not be any need for an end user to register or go through a confirmation process.

RISK
Remember, this means you will not know who is using your software of be able to selectively control access by named user.
Method 2 - Single Account Shared over Multiple Users (e.g. Educational Users)

This method is less risky because you can at least control the account without having the account 'hard-coded' into your application.

We recommend you read this overview to better understand how to apply this technique.

Configuration / Delivery Options

Most customers do not want to create and/or distribute a specific version of their software for educational purposes - and with Nitro-LM you do not have to. By simply setting up a few settings on the NItro-LM server you can control access to your software while minimizing risk of it being used elsewhere without your permission.

Control you have by using either option

The methods outlined below focus on using a single Nitro-LM 'trusted' account that you setup and maintain control over. With either option, you have many options for controlling access to the licenses. Here are a few simple things that you can decide to change at any point in the licensing process to maintain control over the access to the licenses and their users (minimize risk of it being used outside of class by non authorized users).

  • Periodically change the e-mail address
    • requires updates of INCLUDE/EXCLUDE Rules in Nitro-LM
  • Periodically change the password
    • This is a simple account change in Nitro-LM
  • Change the "VALID UNTIL" date for the pool
    • This limits access to a time NEARER than the "PAID TO" Date for the Licenses
    • This would require you to manually move the "VALID UNTIL" Date out for each class.
  • Set the default license type to "Check-Out" Licenses with a fixed duration
    • Short durations (e.g. 1-2 days) will keep the license locally, but give customer options for moving to another machine
    • Longer durations (e.g. 5-15 days) will essentially 'park' the license on the computer like a node locked license would be.
    • Coding the client application to refresh the license on a regular basis (e.g. application startup) will help to keep the license for the software targeted to the machine it is currently loaded on - especially if a check-out license is the default license type
Floating Licenses vs Check-Out Licenses

When a Floating License is the default license type, the client will try to communicate with the Nitro-LM servers on a regular basis. For an educational scenario, this may not be a good thing if the facility has internet connectivity issues. By contrast, a Checked-Out license does not require to call home to the Nitro-LM service, and the application will work without a connection to the internet.

Simple Option - Specific Customer and Pool w/ Trusted e-mail.

Create a Single 'trusted' e-mail account that will be used by all students
  1. Create an e-mail account on your own e-mail server or using a public one (e.g. Google, Yahoo, Hotmail, etc)
    1. This e-mail should only be accessible by you/your organization
    2. This e-mail will be used by students to get licenses for your software, so keep it simple
    • For Example: <CorpID>-TRAINING@google.com (or similar) and password (e.g. training1234)
Setup the Educational Customer and License Pool
  1. Create a New Customer in Nitro-LM specific for educational licenses (e.g. <CorpID>-EDU)
  2. Create a License Pool
    1. Add the total number of licenses you want to allow to the Pool for the product you want to be used
    2. Constrain the default License type for the Pool (e.g. floating or checkout)
    3. Constrain the license pool to ONLY be accessible by your Trusted E-mail
    4. Create an INCLUDE RULE for your trusted e-mail address e.g. <CorpID>-TRAINING@google.com
No need to configure EXCLUDE Rules for this

You do not need to configure an EXCLUDE rule when you have INCLUDE e-mail address(es) applied to a pool. the INCLUDE will only allow specific users access to your licenses. EXCLUDE rules apply when you are doing domain restrictions (e.g. you want to exclude specific users from a company, but allow everyone else to have access).

Register and Confirm the Trusted e-mail Account with Nitro-LM
  1. Use your software's conventional user registration process to register the trusted e-mail address and password with the Nitro-LM Service. This is the same process a normal user would use.
  2. Confirm the trusted e-mail (use the confirmation code and/or the manual confirmation process in Nitro-LM)
Test the License Process
  1. Launch your software application
  2. Attempt to get a license from your newly created CorpID and Pool using the Trusted e-mail/password
    Success? You are ready to send the info to your customer.
    Failed? Re-Check your CorpID, trusted e-mail address and password, then recheck the account settings.
Deliver License Info to Customers

Simply send your customer the following information

  • Trusted e-mail address (e.g. <CorpID>-TRAINING@google.com)
  • Nitro-LM Password for the Trusted e-mail address (e.g. training1234)
  • CorpID for the account (e.g. <CorpID>-EDU)
Why don't I need SEPARATE e-mails/password for EACH student?

Because of the way the account is setup, and because of how Nitro-LM works, you will not need to generate specific e-mails for individual users attending the class. They can all SHARE the same login/password and CorpID information. With these settings, Nitro-LM will allow the same account to be used over multiple machines and users without conflict.

Comments