Enable cross-origin resource sharing (CORS).

To enable Avaya Workspaces to use the on-premise Avaya Aura® Device Services search APIs, enable CORS for the Avaya Workspaces domain.

For more information about configuring CORS, see the following sections in Administering Avaya Aura® Device Services:

• Cross-origin resource sharing

• Enabling Cross-origin resource sharing for the Service Interface

• Enabling Cross-origin resource sharing for the Administrator Interface

Configure single sign-on client ID Mapping.

To support Avaya Workspaces single sign-on flow, you can configure Avaya Aura® Device Services client ID mapping.

For more information about configuring SSO client ID mapping, see the following sections in Administering Avaya Aura® Device Services:

• Prerequisites for Workspaces SSO configuration

• Workspaces SSO Flow configuration

Install Avaya Aura® System Manager, Private, or Third-party CA certificate on the agent's system.

If Avaya Aura® Device Services uses Avaya Aura® System Manager, Private, or Third-party CA certificate, you must install that CA certificate on the agent's system, where the agent uses Avaya Workspaces through the browser.

For more information about certificate issues, see the Avaya Workspaces Client cannot connect to Avaya Aura® Device Services section in Administering Avaya Aura® Device Services.

Configure session count.

For the Avaya Experience Platform™ (On-Prem + Connect) deployment, you must update the value of the Concurrent HTTP session per User field to 135. This configuration change impacts the service and Avaya Aura® Device Services automatically restarts.

For more information about configuring the number of active sessions that are available for each user, see the Managing application sessions section in Administering Avaya Aura® Device Services.