LDAP-UX Client Services B.04.10 Administrator's Guide (edition 7)

Rules that have one of these specified as the <type> field are defining a static list
access rule. For this rule, the <object> field is specified as a predefined list of
identifiers. The identifiers are matched directly with data in the login request. This
<type> field specifies where PAM_AUTHZ will look to determine if the login field
is present in the appropriate data store, such as /etc/passwd, /etc/group, etc.
If the login field is found, the rule is evaluated to be true. The final access right is
determined by the <action> field. See the “Static List Access Rule” section for
details.
other
PAM_AUTHZ ignores any access rules defined in the <object> field. The access
rule is evaluated to be true immediately. For example,
allow:other
In the above example, all users are granted the login access to the machine. The
primary usage of this type of rule is to toggle PAM_AUTHZ default <action>.
ldap_filter
In a role based access management, permission to access a resource can be
controlled based on the user's role such as sales force, technical support or
subscriber status and are typically defined by common business attributes of users
based on company policies. The same concept is applied to the ldap_filter
access rule. A search filter is defined in <object> field. A search filter consists of
one or more (attribute=value) pairs. If the user entry is successfully retrieved from
a directory server by using the search filter, the access rule is considered to be true.
Examples of ldap_filter type of access rule are as follows:
allow:ldap_filter:(&(manager=paulw)(business
category=marketing))
In the above example, if a user reports to paulw and the user's job is related to
marketing, then the user is granted the login access. The rule structure is very
flexible about how to define access for certain groups of users.
PAM_ACCT_EXPIRED:ldap_filter:(nsAccountLock=TRUE)
In the above example, if a user account has been locked out and this access rule is
evaluated to be true, the PAM_ACCT_EXPIRED code is returned by PAM_AUTHZ.
LDAP-UX Client Services B.04.10 or later, PAM_AUTHZ supports dynamic variable
in the ldap_filter type of the access rule. A search filter can consist of one or more
(attribute=$[function_name]) pairs and is defined in the <object> field.
The [function_name] is called and the return value is substituted into the search
filter. Then the search filter is processed the same as the example above. For detailed
information about dynamic variable support, see “Dynamic Variable Access Rule
” (page 108).
status
When status is specified as the <action> field, this defines a rule that is
evaluated to perform account and password policy enforcement. This access rule
defines a library, in the <library_name> field to be loaded, and a function in
the <function_name> field that specifies a function to be invoked to perform
policy evaluation for a particular directory server. See the “Security Policy
Enforcement Access Rule ” (page 110) section for detailed information on the
supported values and usage of this access rule.
<object> The values in this field define the policy criteria that PAM_AUTHZ uses to validate
with the login name. The values in this field are dependent on the option that is
stated in the <type> field.
PAM_AUTHZ Login Authorization 105