/
Applying Authorization Codes

Applying Authorization Codes

Anyone in possession of your floating license authorization code can activate and deactivate seats for your license. Protect the authorization code and share it only with those who need to use it. Profound Logic can deactivate authorization codes on request.

Overview

Upon finalizing a floating license purchase, your salesperson provides a floating license authorization code. This code is how each Profound.js / Profound API instance authenticates to the Profound Logic licensing server in order to claim a seat (see Seat Activation). Authorization codes look like this:

plls_api_1xAeI16MEv7FOZZCqdsmaVsIxsouUWzFchPR8Y4AhqoSLhRZBGuSGFAji7VpDL20wZHYAgxmzQfrJDqlILVRcrQsIIavhQaeFHqg4pUq1hdpnHN6uwKQtZ4

Method 1: Environment Variable (Preferred)

Set an environment variable named PJS_FLOATING_AUTHORIZATION with the authorization code as its value. The variable must be set at instance start up time. This is the preferred method, and it overrides an authorization code stored on the file system.

On IBM i, this is done with the env directive in the instance configuration file (see Starting and Ending Profound.js Instances):

env=PJS_FLOATING_AUTHORIZATION=plls_api_xxx

In a container, it is passed with --env or through a ConfigMap or Secret (see Deploying in Docker Containers / Kubernetes).

Method 2: Authorization Code File

The instance must be restarted after applying an authorization code with the License Key Management page.

The code can also be placed into a text file named floating-auth-code (no extension) on the file system, at a platform-specific location:

  • IBM i - /profoundjs-base/floating-auth-code;

  • Linux and Mac - $HOME/.profoundjs/floating-auth-code, where $HOME is the home directory of the user the server process runs as;

  • Windows - %ALLUSERSPROFILE%\profoundjs\floating-auth-code. %ALLUSERSPROFILE% is a Windows environment variable whose location can vary with the Windows configuration, but is typically C:\ProgramData.

The License Key Management page at http://server:port/key can be used to write the authorization code file to the appropriate location: