Starting the Helix ALM License Server Admin Utility

You need to add licenses and users the first time you start the license server and admin utility. See Adding licenses and Adding users.

Note:  An administrative user is created during installation. Log in as this user the first time you start the admin utility. The username is Administrator and there is no password. To prevent unauthorized access, create a password for this user after you log in.

1. Windows—Choose All Programs > Perforce > Helix ALM License Server > Helix ALM License Server Admin on the Start menu.

Linux—Enter /usr/bin/lsadmin.

The Helix ALM License Server Login dialog box opens.

2. Select the Server you want to connect to. See Adding server connections if you need to add a server.

3. Enter a Username and Password or select Use single sign-on to log in using the workstation credentials. Single sign-on must be enabled and is only available on Windows.

4. Select Always log in with this username and password to automatically log in with the credentials you entered when the admin utility starts.

If you select this option, the license server will automatically use Windows Credential Manager to store your credentials. This option is not available on Linux.

5. Click Connect.

The admin utility starts.

If your organization uses an identity provider, such as Okta, and you are configured to log in to Helix ALM products with it, the provider web page opens. Authenticate with the provider and then return to the admin utility.

If you entered an incorrect password, the Forgot Password? link may be displayed. Click the link to reset your password. You will receive an email with a temporary password and instructions for resetting your password. See Resetting user passwords for information about password resets.

Note:  If RSA key exchange is enabled, you may be prompted to verify the authenticity of the key fingerprint, which is used to prevent hacking. Verify that you are logging in to the correct server. If you are unsure if the fingerprint is correct, log in locally to the computer that hosts the license server and verify that the key displayed in the server options matches the key displayed when you logged in from the other computer. See Configuring RSA key exchange. If the fingerprint is correct, click Yes. If a different fingerprint is displayed in the server options, a hack may be in progress.