Search
Close this search box.
< All Topics
Print

RLM Server Web Interface Passwords v15.1 – v15.2

Overview

Beginning with RLM v15.1 it is mandatory to configure a password file to use the RLM Web Interface. RLM will generate a default password file if there isn’t already a password file present at startup.

Previous versions

RLM versions 10.0 to 15.0 allowed users to create a password file (rlm.pw), but this was optional. Beginning in v15.1 passwords are required to be configured unless the server is run without the web interface enabled (using the -nows parameter at startup).

The older password files are incompatible with the current password file (v15.1+) and will need to be recreated when upgrading from an older RLM version.

Default Credentials

On startup, if a password file isn’t present in the RLM executable directory, RLM will create a password file with the default credentials:

Username: admin
Password: admin

This admin user will have all privileges to the web interface. Users must change this default password within 10 minutes of RLM starting, or RLM will automatically shut down. To change the password:

  1. Log into the web interface using the default credentials.
  2. From the navigation bar choose “Change Password”.
  3. Enter your new password.

Adding new users

New users must be added to the password file with a blank password, and a permission level set. RLM will need to be started/restarted after adding the new user to the password file. Once RLM has been started the user will have 10 minutes to log into the web interface and set a password or RLM will shut down. To set a password:

  1. Log into the web interface using the newly created username, and a blank password.
  2. From the navigation bar choose “Change Password”.
  3. Enter your new password.

User Permissions

A full list of user permission can be found in our documentation here

Categories

RLM and RLM
Activation Pro

What’s the difference?

Reprise License Manager (RLM)

Software License Manager

RLM provides runtime checking that verifies that your application is licensed to run and that the current usage of your application is within the limits you have ser every time your application runs.

As a Software publisher, you integrate RLM into your product, and RLM keeps track at runtime of who is using the licenses of your software.

RLM can do this entirely within the client library (linked into your application), or, more commonly, your application makes a request of the RLM Lincese Server to check out a license.

The lincese server runs either on your customers network, or in the cloud if you are using our RLMCloud™ service.

RLM provides runtime checking that verifies that your application is licensed to run and that the current usage of your application is within the limits you have ser every time your application runs.

RLM Activation Pro

Software Activation Manager

Activation Pro is
used once when your customer purchases your software in order to retrieve the license which is specific to that customer.

Software Activation’s purpose in life is to get the licenses for your product to your customers with a minimum of fuss.

Activation Pro also has a server component wich we call the activation server.

Your application contacts the activation server and supplies a short text activation key, and in exchange, the activation server returns the license which enables your product.

Generally, this is done once, right after your customer purchases your software, not every time your software is invoked.