Parameter
Search mechanism #1:
Find the user, extract the group DNs from
the “memberOf” attribute, and get the
role strings from each of the group
objects
Search mechanism #2:
Find the groups that the user belongs to
and extract the role string from one of
the attributes
Example
Description
Example
Description
This filter looks for a
group object whose
“member” attribute
contains a value of
the authenticating
user DN.
Role Context
DN
ou=Users,dc=global,
dc=example,dc=com
The purpose of the
search is to find the
user and then extract
the role objects from
the “memberOf” user
attribute.
ou=Groups,dc=globa
l,dc=example,dc=co
m
The purpose of the
search is to find the
roles whose
“member” attribute
contains the user.
Role
Attribute ID
“memberOf”
This attribute
contains the list of
DNs of the groups to
which the user
belongs to.
CN
This contains the
group’s name (e.g.
“AAWGAdmin”, etc.)
Role
Attribute is
DN
true
The “memberOf”
values are the DNs
of the group/mailing
list objects.
false
The “Role Attribute
ID” already contains
the “role” string
name.
Role Name
Attribute
CN
The attribute defined
by Role Name
Attribute contains the
group name.
For example:
AAWGAdmin
Leave this empty
because “Role
Attribute is DN” is
false.
Role
Recursion
0
This configuration
does not allow
recursive search.
Note:
Using this
configuration, the
users under the
“AAWGDelegates”
group will not be
able to use Avaya
Aura
®
Web
Gateway so this is
1 or higher
You must set this
value to 0 if there
are no subgroups or
a value from 1 to 10
to support searches
of users that are in
subgroups.
In this example, the
recursive search is
needed to find the
user in the
“AAWGDelegates”
Table continues…
Avaya Aura
®
Web Gateway initial configuration settings
October 2018
Deploying the Avaya Aura
®
Web Gateway
89
