A union of users and resources. ACLs are used to determine which resources (devices and resource managers) a user is allowed to access. When a user has access to a specific set of resources, that user can see data (such as inventory, events, alerts, and analytics) that is related to only those resources.
activation key
A file in .KEY format that is installed to activate a license.
alert
A hardware or orchestrator condition that require investigation and user action.
audit event
A record of user activities that were performed from a resource manager or XClarity Orchestrator.
authentication server
A user registry that is used to authenticate user credentials. See local authentication server and external LDAP server.
authorization code
A 22-character code that is used to generate an activation key for activating a license.
A generic term for a service processor in a server that combines systems-management functions, video adapter, remote presence, and blue-screen capture features in a single chip.
A function that automatically opens a service ticket and sends service data to Lenovo Support when certain serviceable events occur.
component
Part of a platform (such as Lenovo XClarity Controller or Unified Extensible Firmware Interface) on which firmware or software can be applied.
configuration patterns
A set of common configuration settings, including management controller and UEFI firmware settings, that you can use to quickly configure multiple servers at one time.
configured credentials
Client name and password that is used to bind XClarity Orchestrator to the external authentication server. If the bind fails, the authentication process also fails
connection
An authenticated and authorized session with an external resource manager, such as Lenovo XClarity Administrator or a 3rd party service.
Hardware that controls data flow at the boundary between two networks, where data is produced and consumed. These devices do not have baseboard management controllers and require a UDC agent installed on the device to allow management by XClarity Orchestrator. This includes certain ThinkEdge and ThinkCentre devices.
external LDAP server
An LDAP server that resides outside of the XClarity Orchestrator server.
event
See resource event and audit event.
event filter
Rules that define the scope of events that are forwarded to an external application using an event forwarder.
event forwarder
A function that forwarders events to an external application (such as a syslog, email, or REST Web service).
external services certificate
A certificate that XClarity Orchestrator uses to verify that it can trust a server for only specific external services.
export
The process of transferring data from the XClarity Orchestrator to the host system.
User group that is defined in an external LDAP server and cloned in XClarity Orchestrator.
license
Entitlement for service and support and enablement of all orchestrator functions for a specific number of devices.
local authentication server
Embedded LDAP server that resides in the XClarity Orchestrator server.
login credentials
Fully-qualified LDAP distinguished name of a test user account and the password to use for LDAP authentication to validate the connection and bind XClarity Orchestrator to an external authentication server. If successful, all future binds use the username and password that you used to log in to XClarity Orchestrator.
A certificate that XClarity Orchestrator uses to verify that it can trust a resource when that XClarity Orchestrator acts as a client to establish a secure connection to another resource.
A specification that details the interface between the operating system and the platform firmware at boot time. It is not specific to any processor architecture.
update package
A bundle of one or more firmware updates for a specific platform.
update-compliance policy
A set of rules that determine whether certain software or firmware that is installed on a specific resource is at the desired level.
upload
The process of transferring data from the XClarity Orchestrator to the web.
user
A username/password pair that controls access to the product. All users must be assigned to a user group. Each user groups is associated with a role, which identifies the sets of actions that the user is entitled to perform.