Avaya Aura - LDAP configuration

LDAP configuration
If you do not complete LDAP configuration during the initial Avaya Aura
®
Web Gateway setup,
then you can complete it later using the Avaya Aura
®
Web Gateway administration portal as
described in Administering the Avaya Aura
®
Web Gateway.
Warning:
Changing the LDAP configuration parameters, other than Bind DN and Bind Credential, when
they are configured, might invalidate the existing user data. For example, changing how user
roles are found can remove one or more roles from the existing user, which will block the user
from accessing the Avaya Aura
®
Web Gateway system. In addition, do not change the server
URL unless you need to switch the configuration to another replicated instance of the current
LDAP directory. In all the other cases, you must reinstall the Avaya Aura
®
Web Gateway
system.
Table 4: LDAP configuration settings
Item name Description Equivalent properties file parameter
Load LDAP
properties from
file
The Load LDAP properties from file
menu contains an item called Path to
properties file.
You can create a Java properties file that
contains the LDAP properties instead of
entering the LDAP configuration settings
manually. The Path to properties file
option is for configuring the absolute path
to this file.
The LDAP properties file must contain
the equivalent properties file parameters
specified in this table.
The default value for this setting is
<install_dir>/config/
ldap.properties, where
<install_dir> is the installation
directory.
pathToLdapPropertiesFile
Import Secure
LDAP trusted
certificate
The Import Secure LDAP trusted
certificate menu contains the following
items:
• Certificate file: The path and filename
for the LDAP trusted certificate. The
certificate file must be in the .PEM
format.
• Truststore Password: The password
for Tomcat truststore.
LDAP_TRUSTSTORE_CERTFILE
LDAP_TRUSTSTORE_PASSWORD
Table continues…
Avaya Aura
®
Web Gateway initial configuration settings
October 2018 Deploying the Avaya Aura
®
Web Gateway 77
Comments on this document? infodev@avaya.com