Administering Avaya Aura® Device

Services

February 9, 2023
Administering Avaya Aura® Device Services

Notices
© 2023 Avaya Inc. All Rights Reserved.

You may, at your own risk, assemble a MyDocs collection solely for your own internal business purposes,
which constitutes a modification to the original published version of the publications. Avaya shall not be
responsible for any modifications, additions, or deletions to the original published version of publications. You
agree to defend, indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all
claims, lawsuits, demands and judgments arising out of, or in connection with, your modifications, additions or
deletions to the publications.

A single topic or a collection of topics may come from multiple Avaya publications. All of the content in your
collection is subject to the legal notices and disclaimers in the publications from which you assembled the
collection. For information on licenses and license types, trademarks, and regulatory statements, see the
original publications from which you copied the topics in your collection.

Except where expressly stated by Avaya otherwise, no use should be made of materials provided by Avaya on
this site. All content on this site and the publications provided by Avaya including the selection, arrangement
and design of the content is owned by Avaya and/or its licensors and is protected by copyright and other
intellectual property laws including the sui generis rights relating to the protection of databases. Avaya owns all
right, title and interest to any modifications, additions or deletions to the content in the Avaya publications.

February 9, 2023 Administering Avaya Aura® Device Services

Logging in to the Avaya Aura Device Services web administration portal

Logging in to the Avaya Aura Device Services web

administration portal

About this task

You can access the Avaya Aura® Device Services web administration portal by using the Avaya Aura® Device
Services URL or System Manager. To use System Manager for single sign on, you must add the Avaya Aura®
Device Services instance to System Manager.

Before you begin

In the DNS, add an entry to map the IP address with the FQDN.

If the FQDN does not resolve through DNS, you must add the Avaya Aura® Device Services IP address and
FQDN in the hosts file of the system from which you are accessing the Avaya Aura® Device Services web
administration portal. The default path of the hosts file on a Microsoft Windows system is C:\Windows
\System32\drivers\etc\hosts.

Procedure
1. Open the web browser.
2. Type the URL in one of the following formats:
• https://<FQDN>:8445/admin/
• https://<IP_Address>:8445/admin/
If IPv6 support is enabled you can use either IPv4 or IPv6 addresses.
The following are URL examples:
• IPv4 address example: https://10.123.33.44:8445/admin
• IPv6 address example: https://[2001:db8:b99::7334]:8445/admin
3. Press Enter.
If your browser does not have a valid security certificate, the system displays a warning with instructions to
load the security certificate.
4. Optional: If you are certain your connection is secure, accept the server security certificate to access the
Login screen.
5. On the Login screen, enter your user name and password.
To access the web-based administration portal, use an account with an administrator role defined in the
LDAP server configuration.

Note:

February 9, 2023 Administering Avaya Aura® Device Services 3

Logging in to the Avaya Aura Device Services web administration portal

If OAuth is enabled on Avaya Aura® Device Services and LDAP authentication for OAuth is disabled, then
you must use the credentials of the administrative user created during OVA deployment. For more
information about enabling LDAP authentication, see Enabling LDAP authentication for OAuth.
6. Click Log on.

February 9, 2023 Administering Avaya Aura® Device Services 4