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:

An asterisk ( * ) matches 0 or more characters and a question mark ( ? ) matches one character. For example, *AB\*M* matches *ABCDM* and *ABM*. *AB?M* matches *ABCM* but not *ABCDM*.
Control code /c switches off case\-sensitivity and /C switches on case?sensitivity matching. The default is on. For example, */cABC* matches *abc*. */ca/Cbc* matches *Abc* but not *ABC*.
Pattern matching characters, such as the asterisk and question mark, are included in the text to be matched by prefixing them with a forward slash ( / ) character. For example, *A/\*B* matches *A\*B*. *A//B* matches *A/B*.
Variable name *$RMTUSER* can be included in the value. The variable name itself is not case sensitive. *$RMTUSER* and *$rmtuser* are the same. The *$RMTUSER* variable value is the user name with which the remote user is executing. It is the same value used in matching the REMOTE\_USER field.

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.

Windows

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:

An asterisk ( * ) matches 0 or more characters and a question mark ( ? ) matches one character. For example, AB*M matches ABCDM and ABM. AB?M matches ABCM but not ABCDM.
The comparison is case insensitive.
Pattern matching characters, such as the asterisk and question mark, are included in the text to be matched by prefixing them with a forward slash ( / ) character. For example, A/*B matches A*B. A//B matches A/B.

REQUEST_NAME

The REQUEST_NAME field matches the name of a Universal Command Manager is request. The REQUEST_NAME value has the following syntax:

An asterisk ( * ) matches 0 or more characters and a question mark ( ? ) matches one character. For example, AB*M matches ABCDM and ABM. AB?M matches ABCM but not ABCDM.
Case sensitivity depends on the REQUEST_TYPE and the operating system on which the Universal Command Server is executing. See the Server's Security section for the operating system in question.
Control code /c switches off case-sensitivity and /C switches on case?sensitivity matching. The default is on. For example, /cABC matches abc. /ca/Cbc matches Abc but not ABC.
Control code /s normalizes spaces and /S does not normalize spaces. Space normalization removes preceding and trailing spaces as well as reduce consecutive multiple spaces to a single space. The default is no space normalization. For example, /sa b c matches a b c. /Sa b c matches a b c but not a bc.
Pattern matching characters, such as the asterisk and question mark, are included in the text to be matched by prefixing them with a forward slash ( / ) character. For example, A/*B matches A*B. A//B matches A/B.