8.5.101.07
Configuration Server 8.5.x Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 05/05/17 | General | X | X | X | X |
Contents
Helpful Links
Releases Info
Deployment Procedure
Secure Network Logging Deployment Procedure
Product Documentation
Genesys Products
What's New
This release contains the following new feature or enhancement:
- Keep-Alive mechanism for LDAP external authentication: You can increase the robustness of the external authentication connection by enabling this Keep-Alive mechanism (where supported by the operating system). For more information about this new functionality, refer to "Network Connectivity Options for LDAP" in the Framework External Authentication Options Reference Manual.
- Support for Microsoft SQL Server 2016 database. See the Framework page of the Genesys Supported Operating Environment Reference Guide for more detailed information and a list of all supported databases.
Resolved Issues
This release contains the following resolved issues:
Configuration Server can now handle a message that is received in an incorrect format, and no longer terminates unexpectedly as a result. (MFWK-18713)
When Configuration Server restarts, it now reads the log options set in its Application object. Previously in this scenario, it ignored the log options set in its Application object and read the log options in its configuration file. (MFWK-18270)
When the URL of an LDAP Server is is specified using incorrect syntax in the ldap-url option in [gauth_ldap] and [gauth_ldap-<n>] sections, Configuration Server now rejects this value and continues to use the previous value (if available). Previously in this scenario, Configuration Server sometimes tried to connect to the LDAP Server on the localhost instead. (MFWK-18242)
When using LDAP external authentication, CPU usage by Configuration Server no longer rises to excessive levels, now that a single internal timer is used to handle the processing of all responses from the LDAP Server. Previously, one timer was used to handle each login attempt, meaning that there could be multiple timers waiting for responses from the LDAP Server, all increasing CPU usage. (MFWK-18066)
Upgrade Notes
No special procedure is required to upgrade to release 8.5.101.07.