Restricting License Server Administration

You can restrict access to server administration operations by creating an administration authorization file (admin_auth) that is stored on a specific license server. This file specifies machines and users: only the users listed, when logged into the machines listed, can perform server administration operations on that server.

The following operations are restricted:

  • Add License
  • Revoke License (however, users who are already using licenses can always revoke their own licenses)
  • Change Maintenance Expiration
  • Change License Expiration
  • Deregister License
  • Clear License File
  • Update System Date
  • Start Server
  • Stop Server

WARNING: If you do not create an administration authorization file, any user from any machine has access to these operations.

The administration authorization file is a text file with the following format:

<machine> <user>
...
<machine> <user>

You can use a plus sign (+) to mean any user or any machine, as shown in the following example.

engineering1 root
js_pizza_box jsmith
ww_NT wwilson
+ hhoover
engineering_test +

This example file shows that:

  • any user logging in as root on engineering1 can perform server administration operations
  • jsmith can perform operations when logged into js_pizza_box
  • wwilson can perform operations when logged into ww_NT
  • hhoover can perform operations when logged into any machine
  • any user can perform operations when logged into engineering_test

Name the administration authorization file as admin_auth and place it on the license server for which you want to control administration operations, in the same directory as the license file:

Windows: <primary_hard_drive>:\OPNET_license\ Linux: /opt/OPNET_license/

After adding or editing an administration authorization file, you must do one of the following things to make it take effect:

  • In the License Manager, choose Tools > Refresh Server Authorization Files.
  • Stop and restart the license server