|Maintenance Notice - PDF Generation|
|Dynamic PDF generation for web-based content is temporarily unavailable. This maintenance affects dynamic PDF files that are generated from either the HTML-based page or manual that you are viewing. Links that normally allow this functionality have been hidden, and will reappear as soon as the feature is restored.
Network and Security Considerations
Login Authentication Requirement
Workbench uses Genesys Configuration Server authentication. To login to Workbench, each user needs a valid Configuration Server user ID and password with Read and Execute permissions to use the Workbench Client application.
Workbench supports secure TLS (Transport Layer Security) connections for communication between the Workbench Server and the Workbench Client running in a web browser. For instructions on enabling this, see the “Configuring HTTPS for the Workbench Client” section on the Provisioning Workbench Client page.
Workbench supports TLS connections to all Management Framework components (Configuration Server, Message Server, and Solution Control Server). For instructions on configuring secure connections, see the Genesys Security Deployment Guide.
Secure TLS connections are supported between these Workbench components:
- Workbench Server and Workbench Agent
- Workbench Server and Workbench Log Extractor
To enable TLS connections between Workbench components, ensure the trust store and key store configuration options are defined for each component. See “Configuring HTTPS for the Workbench Client” as well as the Workbench Server and Log Extractor configuration options sections for details.
Running Workbench can affect network performance. Please read the documentation carefully before deploying Workbench in a production environment. Be aware that Workbench will consume network and application server resources.
Data collected by Workbench (including metrics, alarms, changes in configuration files, and log events) is stored locally in the customer environment. The customer is responsible for protecting this data.
Outbound Network Connectivity Requirements (RAM Subscribers)
In some customer environments, outbound network connectivity is restricted. If you subscribe to the Remote Alarm Monitoring (RAM) service from Genesys Care, you will need to enable minimal connectivity for Workbench to send alarms from the Remote Alarm Monitoring service to Genesys for processing. This processing includes routing alarms to Genesys support analysts and displaying alarm notifications in the Genesys Care Mobile App.
The outbound connectivity should allow the Workbench Server to reach alarm.genesys.com (188.8.131.52) on port 443. You may need to engage your networking or security team to enable this connectivity.