Personal Licenses

RLM’s Personal Licenses are licenses that are locked to a particular username with an optional hostname. They are much like user-based or named-user licenses, however your customer is able to maintain the user list via the RLM Cloud portal’s GUI. Actually, you have the option of allowing your customer to maintain the list, or you can maintain it, depending on whether you give your customer access to the portal or not.

RLM Personal Licenses are available using RLM Cloud license servers only.

In order to provision a particular customer, browse to the RLM Cloud portal (known as the “RLM Cloud Control Customer Portal”), then select the Personal Licenses tab, located under the Admin tab. Next, if there is more than one product using personal licenses, select the product. At this point, you will see a form that allows you to enter the customer’s name/password/options. When complete, press Save User List at the bottom. This will save the currently displayed page only. You can also cancel if you have made a mistake, or re-select the product using the buttons at the bottom of the form.

There will be as many “user slots” as there are licenses for this product.


How to use Personal Licenses in your application

If you want to use personal licenses you do 2 things:

  1. Create a license with the keyword “personal=NNN”, where NNN is the # of personal licenses. NNN should match the count on the LICENSE line.

  2. In your application, gather the user’s username and password, using whatever method is appropriate. Force the username (including the hostname) to lowercase. Set the username and hostname using the rlm_set_environ() call, and set the password using the environment variable RLM_PERS_PW, using a call similar to rlm_putenv(“RLM_PERS_PW=your-user’s-password”);

So, for example, if your user’s name is “testuser@testhost.com” and the password is “testpw”, make the following 2 calls:

  • rlm_set_environ(handle, “testuser”, “testhost.com”, “”);

  • rlm_putenv(“RLM_PERS_PW=testpw”);

Note

Personal licenses and Dynamic reservations use the same variables for transport, so it is not possible to have a personal license that uses dynamic reservations. This is a minor restriction, since the use cases for these 2 kinds of licenses are so completely different.