8.6.000.09
Web Services and Applications Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Mac | Solaris | Windows |
|---|---|---|---|---|---|---|---|
| 02/21/25 | General | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- Genesys Web Services (GWS) now supports Transport Layer Security (TLS) on all its interfaces. You can enable TLS by configuring the following options:
- ElasticSearch setting:
- verifyPeer - This setting ensures that the SSL/TLS connections to ElasticSearch verify the peer's certificate for enhanced security. By default, this option is set to true.
- If you want to set the value to false, in the application.yaml file of the GWS 8.6 application, add the verifyPeer parameter in the elasticSearchSettings section. For example,
elasticSearchSettings: verifyPeer: true/false
- verifyPeer - This setting ensures that the SSL/TLS connections to ElasticSearch verify the peer's certificate for enhanced security. By default, this option is set to true.
- TLS settings for GWS Platform Service
- To establish a HTTPS connection with GWS Platform Service, configure the platform service URL in the application.yaml file as shown in the following settings:
serverSettings: platformSettings: platformServiceUrl: https://<ip>:<port>- Also, make sure that configured CA (Certification Authority) certificates are added to the JKS (Java KeyStore) file.
serverSettings: caCertificate: /opt/ca_cert.jks #location of the file jksPassword: pa$$word #password for the keystore
- Valkey Support
- GWS now supports both Valkey Redis 7.2 and Redis 7.2, providing greater flexibility in database options.
- TLS Support in GWS Platform Service
- GWS Platform Service now supports TLS and the following new Environment variables support configuring TLS.
- ElasticSearch setting:
| Name | Mandatory | Default Value | Description |
|---|---|---|---|
| GWS_SERVER_TLS_REQUIRED | No | false | Determines if TLS is required. Change to true if a certificate is also provided. |
| GWS_SERVER_TLS_PROVIDER | No | rustls | Specifies the TLS provider. Possible values: rustls, native. |
| GWS_SERVER_TLS_HANDSHAKE_TIMEOUT | Yes (if TLS is enabled) | 10000 (ms) | Specifies the timeout (in milliseconds) for TLS handshake. Default is 10000 ms (10 seconds). |
| GWS_SERVER_TLS_CERT_PATH | Yes (if TLS is enabled) | - | Specifies the path to the TLS certificate. |
| GWS_SERVER_TLS_KEY_PATH | Yes (if TLS is enabled) | - | Specifies the path to the TLS key. |
| GWS_AUTH_TOKEN_IDLE_TIME | No | - | Specifies the idle time (in seconds) before an auth token is considered inactive. If absent, all tokens remain active until expiration. |
| GWS_SERVER_TLS_CERT_PASSWORD | No | "" | Specifies the password for the TLS certificate, if applicable. |
Resolved Issues
This release contains the following resolved issues.
Agents can now store the draft/inbound emails in the appropriate workbins even though non-target workbins that cannot be viewed existed in an environment. Previously, in such scenarios, agents were not able to store the draft/inbound emails in the workbin. (GWS86-1210)
Certificate validation now correctly bypasses the Subject Alternative Name (SAN) validations when verifyPeer:false is set for Redis in the application.yaml file. Previously, in such scenarios, SAN validation was not fully disabled that resulted in displaying warning messages about mismatched SANs for Redis. (GWS86-1137)
An empty device list is no longer displayed for users logging in without a default place assigned to them, and the /me/devices API no longer returns 'no devices error' for such users. An error in the dynamic hot-place assignment functionality has been fixed. (GWS86-1203)
Upgrade Notes
No special procedure is required to upgrade to release 8.6.000.09.