...
| Table of Contents | ||
|---|---|---|
|
Named-User Licenses
Named-User licenses allow for tokens to be reserved for and assigned to specific users. They can be reserved for users ahead of time and/or left unreserved and available to any user not currently denied access to reserve on a first-come, first-served basis. Token reservations for named-user licenses do not naturally expire and must be manually released.
...
How Identical Usernames from Multiple Machines are Handled
The behavior depends on whether Grant multiple tokens to same username is enabled for the license.
Suppose you have a two-token, named-user license user license and the following scenario occurs:
- User "test" from machine1 requests a license.
- User "test" from machine1 is issued a token.
- A few seconds later, user "test" from machine2 requests a license.
...
If Grant multiple tokens to same username is enabled, user "test" from machine2 will be issued the second token.
If Grant multiple tokens to same username is not enabled, user "test" from machine2 will be denied a token, even though there is one available.
For more information about reserving and releasing named-user license user license tokens, see Reserving Licenses.
Unusual Use Case
There is an unusual use case for you to be aware of. In this scenario, Grant multiple tokens to same username is enabled and user "test" has two reservations as described above, then Grant multiple tokens to same username is disabled. In this situation, user "test" will be able to get two tokens (or as many tokens as allowed by the reservations). If you no longer want user "test" to get multiple tokens, remove the existing reservations.
Floating Licenses
Floating licenses allow for X number of users to use the tool concurrently, where X is equal to the number of tokens. Tokens can be reserved for users who match a user pattern and/or host pattern or who belong to a pre-defined group and/or they can be left in an open license pool to be claimed on a first-come, first-served basis.
...
For more information about reserving and releasing floating licenses, see Reserving Licenses.
Machine-Locked Licenses
Machine-locked licenses allow for tokens to be reserved for and assigned to specific machines. All machine-locked licenses are single-token licenses and that token can be reserved for a specific machine ID or left in a pool to be claimed in a first-come, first-served basis. Once reserved, the token does not naturally expire and must be removed manually, but this can only be done after a 30-day waiting period has passed.
...
For more information about reserving and releasing machine-locked licenses, see Reserving Licenses.
Upgrade Licenses
Upgrade licenses enable you to use the tokens of your base license to access both your current version of a tool and a newer version of that same tool. For example, suppose you originally purchased a 10-token license for a tool and eventually upgrade to the new version of that tool, but you're not ready to upgrade your entire infrastructure to the new version yet. By getting an upgrade license and linking it to the base license, you can use any or all of your tokens to access both versions of the tool at the same time. You might have four tokens reserved for the older version of the tool and six tokens reserved for the newer version. In this scenario, the license you originally purchased for the tool is the "base license" and the license for the new version is the "upgrade license."
...