Configure On-Premise License Manager
How to open the Settings dialog
Open the On-Premise Licensing Portal in your browser, and log in with the system administrator user name and password you specified during the Install On-Premise License Manager.
On the On-Premise Licensing Portal, click
Configure Settings at the top right:
The Configure Authentication Method dialog box will appear:
Note
To open the On-Premise License Server in your browser, use: license-server-address:port, for example, localhost:40892.
Method
The Method tab (pictured above) allows you to select the preferred option to access the server. When the Access for everyone is selected, the License Server is configured as follows:
It gives a license seat to any user registered in your network domain for all licensed products.
Access for Everyone allows any user without authorization to acquire a lock for a license.
License admins do not need to assign licenses to users in the Licensing Portal.
License admins cannot revoke a license from a given user.
Users don’t need to enter their credentials to get a license seat.
All users appear as anonymous.user in the Licensing Portal.
See below for LDAP and OIDC descriptions.
Configure for anonymous users
System admin can now configure the anonymous users and control how much license session information anonymous users view. In Access for Everyone mode, users connect without authentication, and the licensing portal identifies each session as an anonymous user. By default, anonymous users see only basic license information: the license number, expiration date, allowed concurrent users, idle time, and license status.
Important
These settings apply only in Access for Everyone mode. They do not affect License Management operations with Lightweight Directory Access Protocol (LDAP) or OpenID Connect (OIDC) authentication.
A system administrator can grant anonymous users the following permissions:
Allow anonymous users to view locking details shows the username and machine name for each active session.
Allow anonymous users to disconnect users and allow the users to disconnect a session and return the license to the available pool.
System administrators can view the detailed session details, including the machine name and the username of the account signed in on the client computer, regardless of how anonymous user settings are configured.
Configure Anonymous User Settings
To configure the anonymous user settings, do the following:
Sign in to SmartBear License Management as a system administrator.
On the license page, select the Anonymous user settings icon.
In the Anonymous user settings dialog box, turn on either or both of the following settings:
Allow anonymous users to view locking details: Anonymous users can view the username and machine name for each active session, but cannot release a license.
Allow anonymous users to disconnect users: Anonymous users can disconnect an active session and release the license it holds.
Note
Anonymous users can see who holds each license but cannot release it unless the administrator also turns on Allow anonymous users to disconnect users toggle.
Click Save.
Disconnect an Active Session
To release a license held by an active session, do the following:
In the Users list, locate the session you want to disconnect.
In the Disconnect User dialog box, click Disconnect.
The licensing portal refreshes automatically and returns the license to the available pool. System administrators can disconnect any session. Anonymous users can disconnect a session only when the Allow anonymous users to disconnect users toggle is turned on.
Non-standard LDAP configurations
SmartBear uses the following default LDAP configuration values:
usernameField: sAMAccountName
emailField: mail
firstNameField: givenName
lastNameField: sn
groupNameField: distinguishedName
memberOfField: memberOf
userQueryPrefix: (objectClass=user)
groupQueryPrefix: (objectClass=group)
For non-standard LDAP configurations, the mapping must be adapted. For example, if your configuration uses a custom group, instead of the default group for user groups in AD, you must define how this object class is interpreted.
Follow the set-up steps below. They are for Windows (Linux steps are similar). If you need assistance, open a ticket with Support.
Stop the licensing service if it is running.
Edit the
Smartbear/LicenseManager/bin/slm_service.vmoptionsfile and add custom configuration entries in separate lines. Use the following syntax:-Dldap.configName=valueStart the licensing service.
OpenID Connect - OIDC
Settings on the OpenID Connect (OIDC) tab (pictured below) specify the configuration that allows the On-Premise License Server to access information stored in the authentication server.
The On-Premise License Manager implements the authorization code flow and needs to obtain client id and client secret so users can log in with the OIDC identity provider (IDP).
Note
The License Manager must be configured as an application on the OIDC identity provider (IDP) side, for example, Okta. Use the callback URL displayed in the OIDC settings as the redirect URI.
client ID and client secret are unique identifiers that will be used to authenticate the On-Premise License Manager with your OIDC server.
By configuring OIDC:
License administrators can assign license seats to users by users’ names.
Your teammates can log into the Licensing Portal using their OIDC credentials.
 |
Here are definitions for the values requested in the configuration fields:
Field | Description |
|---|---|
Name | Descriptive name of the configuration |
URL | OIDC server URL |
Use PKCE | Toggle the switch to use the PKCE-enhanced Authorization Code Flow. For more information, see Authorization Code Flow with Proof Key for Code Exchange (PKCE) from Okta. |
Client ID | Unique identifier for the On-Premise License Manager on the OIDC server |
Client secret | Unique string paired with the Client ID value for the On-Premise License Manager on the OIDC server |
Scope | Scopes are permissions that your application will need to access user data. You will need to add openid, profile. In some environments, the email scope will also be required. The OIDC server will only grant the scopes that you have requested. |
User Name | Field in the token that contains user data. This depends on you OIDC server configuration. Common fields for storing user data in OIDC tokens include email and name. |
Group Filter Enabled | Toggle the switch to use group filtering and manage access control based on the group membership. |
Group Name Field | Field in the token that contains group data, for example, company or department |
User Group Filter | To grant permissions to resources, add values configured on the OIDC server that match the client's requirements. |
Admin Group Filter | To grant administrator permission, add values configured on the OIDC server that will assign elevated scopes. |
Callback URL to be registered on the OIDC server | Use this URL as the redirect URI in the OIDC server settings. |
Note
The filters in OIDC settings apply only to users authenticated via the OIDC server. Service accounts do not have groups assigned.
Test your configuration.
After configuring the OIDC method, the button shows on the login page. Users must use this button to log in.
 |
For more information on Open Connect ID, see How Open ID Connect Works.
How settings affect user authentication
The License Server settings specify how the Server gets information on user accounts in your network and how it authenticates users. The following table provides a brief overview of the setting effect:
Settings | Required | License admin needs to assign licenses to users on On-Premise Licensing Portal | Users need to enter their credentials on product start |
|---|---|---|---|
Access for everyone | Optional | No | No |
LDAP | Required | Yes | Yes |
OIDC | Required | Yes | Yes Log in with OIDC is added as a login option |
Save or discard changes
The Save button on a page remains disabled until you change some settings on this page.
The button saves the changes made to this page only.
After you change a setting on some page, the dialog displays the Discard Changes button (initially, the button is hidden). Click it to discard all the changes made to the settings on this page.
Next steps
After installing and configuring the On-Premise License Server, you can add licenses and assign them to users in your network. See Add Licenses and Assign Licenses to Users.
Change Password
As a system admin, you can change the password for your account. Use the dialog to update your login credentials.
