Jump to: navigation, search

Network and Security Considerations

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

TLS Security

Workbench uses 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.

Network Considerations

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. Capacity planning is strongly recommended before deploying Workbench.

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 ( on port 443. You may need to engage your networking or security team to enable this connectivity.

This connectivity requirement only applies if you are using the Remote Alarm Monitoring Service with Workbench.
This page was last edited on November 29, 2019, at 14:41.


Comment on this article:

blog comments powered by Disqus