IAUG Feature Request Tracker

The deployment templates for the various Aura OVAs do not make consistent requests for information. Some ask for FQDN, some ask to break out the domain and hostname. It would be nice to have a consistent deployment experience across all Aura products.

Within the menus of SMGR is the ability to duplicate a station, but not to duplicate an agent. To provide a junior administrator that ability requires enabling them to use Element Cut Through, which effectively gives them Profile 18 permissions on CM.

Show last update date and user name for administrative changes

When a user has setup the SSO to allow a Workplace or J100 series phone to login using the corporate IAM rather than a known username and password, there should be an option to allow AADS to scramble or reset the password on each successful login attempt. Business Case: New requirements of PCI-DSS require passwords to be rotated on a regular basis, including those device-to-machine and user-to-machine passwords that aren't set by a user themselves. By rotating the password on each successful login, the password will remain new. The SSO login portion of AADS allows the user to login with their known credentials; they are not given or exposed the actual internal password used by ASM/SMGR/AADS. This request would enhance security and will for compliance while still allowing the enterprise to manage the user's password separately.

Please add the ability to start a remote control session by directly clicking on the Agent in the Enterprise Agent list (and RW Agent list).

Is Avaya interested in evolving how administrators/users login to each servers rather than logging into each application individually? Can all aura stack (UC and CC) be integrated with Active Directory with 2FA/MFA (forgerock) for SSO rather than logging into each server and create account.