User-Based Licensing User Guide

Document ID: 102516_1.1_00_en

Version 1.1

User-Based Licensing overview

• A failed test returns a non-404 error, such as, connection timeout, server unreachable, and so

on. If this happens, check to see if a firewall is preventing access to these websites.

Network requirements for license server

Users require access to the user-based licensing license server set up by your local administrator.

2.5 User-Based Licensing terminology

Describes the terms used in Arm® user-based licensing documentation.

The following terms are used in user-based licensing documentation:

Activation

The act of fulfilling an entitlement for a specific user. The output of an activation is a license.

Activation code

Sequence of letters and digits, formatted as a Universally Unique Identifier (UUI), which

represents a seat of a product entitlement for a specific end-user or service account.

Cached license

The locally stored license information. This license is valid for 30 days but is extended when

your Arm product successfully connects to the license server or activation code URL.

Device

Generic term for all computing devices capable of running Arm software products. This can

be a workstation, a virtual machine, a server, or a mobile device such as a phone or a tablet.

End-user

A person interacting with the Arm product software.

Floating

A license that is held centrally and handed out on-demand, checked out, to clients. The

license is checked out for the duration that a license-managed feature is in use, and ends

with the license being checked back in. A floating license is locked to a license server that

serves the license to clients. This model is referred to as a concurrent licensing model,

because it enforces maximum concurrent use. Unless the license is borrowed or cached, the

client must maintain a network connection with the license server for the entire duration that

the license-managed feature is in use.

License

Output of an activation, representing an entitlement for a user. A license is also referred to

as a certificate. A license is typically stored on the local file system of the device used when

activating your Arm software product.

License server

A local server used to activate licenses.

Node-locked

A license that is locked to the device where the license-managed software runs. This model is

referred to as a device-based licensing model.

Copyright © 2022 Arm Limited (or its affiliates). All rights reserved.

Non-Confidential

Page

10 of 19