Secured Functionality on the License Server
When administrative security is enabled on the license server, the following license server operations require credentials:
|
•
|
Resetting your administrator password |
|
•
|
Creating and managing other enterprise user accounts |
|
•
|
Adding and deleting license reservations |
|
•
|
Setting or resetting license server policies, including administrative security policies |
|
•
|
Suspending and resuming the license server |
|
•
|
Manual initiating a binary exchange between the license server and the back office, such an online or offline activation or synchronization event |
Additionally, “read” operations might also require credentials, depending on how administrative security is configured on the license server. Refer to the next section Policy Affecting “read” Security for more information.
For references to the appropriate documentation describing how you provide credentials when using a specific administrator tool, refer to the previous Security Work Flow in the Enterprise section.
Operations Exempt from Administrative Security
The following operations are always exempt from administrative security measures (that is, no credentials are ever needed to perform these operations):
|
•
|
Binary exchanges between the license server and FlexNet Operations that are initiated by the license server, such capability-polling exchanges and synchronization at set intervals |
|
•
|
Binary exchanges between the license server and license-enabled clients |
Policy Affecting “read” Security
When administrative security is enabled on the license server, it uses the security.anonymous license-server policy to determine whether users need to provide credentials simply to “read” information—such as current reservations, features, licenses, or status—on the license server. See Administrative Security Policies on the License Server for more information.