Request Identification
In addition to the client identity being used to search for UACL entries, the client's request may be part of the matching criteria. The exact request fields used are dependent on the component's UACL entry type.
Request Fields
The following table lists a complete set of possible request fields. See each component's UACL entry definitions for further details.
Field | Description |
|---|---|
LOCAL_USER | Matches the local user name with which the remote user is requesting to execute as on the local host. LOCAL_USER value has the following syntax:
A space character delimits the variable name, or it can be enclosed in parentheses (for example, $(RMTUSER)), in which case it is delimited by the right parenthesis. This is useful if it is immediately followed by text. For example, if the remote user name is TOM, a LOCAL_USER value of $RMTUSER will match if the local user name requested is also TOM. A LOCAL_USER value of $(RMTUSER)01 will match if the local user name requested is TOM01. tip The LOCAL_USER value is not case sensitive, since Windows user account names are not case sensitive. |
REQUEST_TYPE | Matches the type of request a Universal Command Manager is requesting. The REQUEST_TYPE value has the following syntax:
|
REQUEST_NAME | The REQUEST_NAME field matches the name of a Universal Command Manager is request. The REQUEST_NAME value has the following syntax:
|