LDAP type

Avaya Aura® Device Services supports the following LDAP types:

• Microsoft Active Directory 2012, 2016, and 2019

• Microsoft Active Directory Lightweight Directory Services (LDS) 2012

• IBM Domino Server 7.0 and 8.5.3

• Novell e-Directory 8.8

• Open LDAP 2.4.44 and 2.4.46

• Oracle Directory Server Enterprise Edition 11g Release 1 (11.1.1.7.0)

• ActiveDirectory_2022

• Azure Active Directory

Additional LDAP parameters

• LDAP URL

• Bind DN

• Bind Credential

• UID Attribute ID

• Base Context DN

• Role Filter

• Role Context DN

• Role Attribute ID

• Role Recursion

• Search Scope

• User IDs for administrator role, users role, and auditor role

• Active users filter

For examples of LDAP parameters, see LDAP configuration or Examples of Microsoft Active Directory LDAP property files.

System Manager FQDN

If you deploy Avaya Aura® Device Services in an environment with Avaya Aura®, you must know the System Manager FQDN.

If you deploy Avaya Aura® Device Services in an environment without Avaya Aura®, this parameter is not required.

System Manager enrollment password

If you use System Manager for enrolling certificates, ensure that you have the enrollment password.

To view the enrollment password, go to the System Manager home page, and click Security > Enrollment Password to check whether the enrollment password expired. If the Time Remaining field displays zero, the password expired and must be changed.

If you deploy Avaya Aura® Device Services in an environment without Avaya Aura®, this parameter is not required.

Session Manager Asset IP

If you deploy Avaya Aura® Device Services in an environment with Avaya Aura®, you must know the Session Manager Asset IP address.

To view the Session Manager Asset IP address, go to the System Manager home page, and click Session Manager > Session Manager Administration. In the Session Manager Instances tab, select a Session Manager instance, and click View. You can see the Session Manager asset IP address in the SIP Entity IP Address field.

If you deploy Avaya Aura® Device Services in an environment without Avaya Aura®, this parameter is not required.

Session Manager management IP address

If you deploy Avaya Aura® Device Services in an environment with Avaya Aura®, you must know the Session Manager management IP address. To view the Session Manager management IP address, go to the System Manager home page, and click Session Manager > Session Manager Administration. In the Session Manager Instances tab, select a Session Manager instance, and click View. You can see the Session Manager management IP address in the Management Access Point Host Name/IP field.

If you deploy Avaya Aura® Device Services in an environment without Avaya Aura®, this parameter is not required.

Keystore password

Set this when running the binary installer to any password of 6 characters or more.

Avaya Aura® Device Services CLI user name

When running the binary installer, use the same user name that you specify when deploying the Avaya Aura® Device Services OVA.

Avaya Aura® Device Services CLI password

While running the binary installer, use the same password that you specify while deploying the Avaya Aura® Device Services OVA.

Number of deployment nodes

Avaya Aura® Device Services supports single node and multiple node deployments. Use the profile chosen during Session Manager deployment and the number of users you need to support to determine how many nodes you require.

IP addresses and FQDNs

For every N Avaya Aura® Device Services nodes to be deployed, you must have N+1 IP addresses: one address for each node and one virtual IP address.

For example, for deploying 3 nodes, you must have 4 IP addresses: one for each node and one IP for the virtual IP address.

Third-party CA certificates

You must use identity certificates signed by a third-party Certificate Authority if you:

• Deploy Avaya Aura® Device Services in an environment without Avaya Aura®.

• Do not want to use identity certificates that System Manager issues in an environment Avaya Aura®.

Avaya Aura® Device Services requires the following four identity certificates:

• REST interface certificate.

• OAMP interface certificate.

• Node certificate for internode communication.

You must also have root and, if used, intermediate third-party CA certificates.