Release Note

Configuration Server

8.1.x

Genesys Telecommunications Laboratories, Inc. © 2011–2016

Contents

Introduction

Release Number AIX HP-UX PA HP-UX IPF Linux Solaris Windows
8.1.300.29 [07/01/16] – Hot Fix       X    
8.1.300.27 [03/11/16] – General X     X X X
8.1.300.26 [11/05/15] – Hot Fix X     X X X
8.1.300.24 [04/24/15] – Hot Fix       X   X
8.1.300.23 [04/24/15] – Hot Fix X     X X X
8.1.300.22 [02/18/15] – General X     X X X
8.1.300.21 [02/06/15] – General X     X X X
8.1.300.19 [12/05/14] – Hot Fix X     X X X
8.1.300.18 [07/10/14] – Hot Fix X     X X X
8.1.300.17 [05/14/14] – Hot Fix       X X X
8.1.300.16 [12/03/13] – Hot Fix X     X   X
8.1.300.14 [09/10/13] – Hot Fix       X X X
8.1.300.12 [08/08/13] – Hot Fix X     X X X
8.1.300.09 [07/03/13] – General X X X X X X
8.1.200.26 [02/10/14] – Hot Fix       X   X
8.1.200.25 [07/05/13] – Hot Fix       X   X
8.1.200.24 [04/08/13] – General X X X X X X
8.1.200.22 [02/21/13] – General X X X X X X
8.1.200.18 [12/07/12] – Hot Fix X X X X X X
8.1.200.17 [11/21/12] – General X X X X X X
8.1.100.18 [10/17/12] – Hot Fix X     X   X
8.1.100.17 [09/11/12] – Hot Fix X         X
8.1.100.16 [06/25/12] – Hot Fix       X X X
8.1.100.15 [05/25/12] – Hot Fix       X   X
8.1.100.14 [05/22/12] – General X X X X X X
8.1.100.12 [04/17/12] – Hot Fix       X   X
8.1.100.11 [04/06/12] – General X X X X X X
8.1.000.19 [06/14/12] – Hot Fix       X X X
8.1.000.18 [04/13/12] – Hot Fix       X   X
8.1.000.17 [01/27/12] – Hot Fix X     X   X
8.1.000.16 [11/16/11] – General X X X X X X
8.1.000.15 [10/11/11] – Hot Fix       X    
8.1.000.14 [07/13/11] – General X X X X X X

Link to 8.0 Product Release Note (Cumulative)
Documentation Corrections
Known Issues and Recommendations
Discontinued Support
Internationalization
Additional Information


Introduction

As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesys.com for more details.

This release note applies only to the 8.1 releases of Configuration Server that are specified in the Contents (above).

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information about third-party software used in this product, see the Read Me. Please contact your Genesys Customer Care representative if you have any questions.


Release Number 8.1.300.29 [07/01/16] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Note: Support of Genesys Security Pack on UNIX version 8.5.100.12 or higher was added to this release on December 16, 2016.

Corrections and Modifications

This release includes the following correction or modification:


When using LDAP external authentication, Configuration Server no longer stops authenticating users if one of the two connections that Configuration Server makes to the LDAP server is rejected while the other connection is maintained. (MFWK-17536 [MFWK-17452])


Top of Page


Release Number 8.1.300.27 [03/11/16] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of Configuration Server.

Note: On March 25, 2016, the release type changed from Hot Fix to General.

Corrections and Modifications

This release includes the following correction or modification:


Configuration Server no longer resets an agent's Wrap-up Time when an annex entry of the Agent Login object associated with that agent is changed. Previously in this scenario, Configuration Server reset the Wrap-up Time to zero (0).

This issue was introduced in 8.1.3; it did not occur in earlier releases.

(MFWK-17267)


Top of Page


Release Number 8.1.300.26 [11/05/15] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


Configuration Server now disables external authentication when the library option is set to internal at the Tenant or Person level. Previously, if a Person had a non-empty External User ID, the setting library=internal was given lesser priority, causing Configuration Server to authenticate the corresponding person externally. (MFWK-17014, MFWK-16857 [MFWK-16779], MFWK-16856 [MFWK-16761])


Configuration Server now retains changes to key-value pairs when configuration objects' Annex entries are changed in a way that replaces existing key-value pairs with pairs of another type, while retaining the same key of the pair. Previously in this scenario, Configuration Server stored the changed pairs incorrectly, and the changed pairs did not survive a Configuration Server restart.

One case in which this problem occurred was when privileges were changed through GAX.

(MFWK-16988 [MFWK-16833])


When using LDAP external authentication, Configuration Server uses only the DN (Distinguished Name) attribute returned by LDAP Server in the ldap-url option for each entry searched in LDAP. (MFWK-16965 [MFWK-16902])


When using RADIUS external authentication, Configuration Server no longer logs a large number of RADIUS debug messages if the RADIUS Server is not available. Previously in this scenario, Configuration Server logged the following message a large number of times in succession:

RAD_DBG: ERROR : Socket Error : socket == -1

(MFWK-16956 [MFWK-16426])


When using external authentication, if the LDAP server dropped the connection or returned an unexpected error to Configuration Server, Configuration Server in this case ignored the retry-attempts option, repeatedly reestablishing a connection to the LDAP servers and retrying failed authentication attempts. Configuration Server also did not take into account the age of authentication requests in the queue before resending them to LDAP, increasing the processing load by executing requests that had timed out.

To prevent this, Configuration Server now properly limits the number of retry-attempts as specified by this option. In addition, Configuration Server now limits the time that a client's external (via LDAP) authentication request waits for a response within a given time interval. The time interval is determined by the maximum value of retry-attempts together with retry-interval settings for all specified ldap-url settings.

(MFWK-16955 [MFWK-16631], MFWK-16858 [MFWK-16442])


Restart of the primary Configuration Server no longer results in the primary and backup servers both running in primary mode. Previously, this problem occurred in very rare cases, and was timing dependent. One scenario was when the restarted primary Configuration Server assumed the primary role before the backup Configuration Server instance completed its switch to primary mode, initiated by the Management Layer due to the restart of the original primary Configuration Server. This issue was sometimes caused by the deletion of a configuration object through the restarted primary, or the temporary loss of the Configuration Server connection to the database or DB Server. (MFWK-16947 [MFWK-16484])


In a high-availability (HA) configuration, if you start the backup Configuration Server Proxy while the primary server's host is not available, the backup server now properly switches to primary mode. Previously in this scenario, the backup Configuration Server Proxy sometimes stopped responding and did not switch to primary mode. When this happened, you had to manually perform the switchover using the Solution Control Server utility mlcmd or manually start the primary Configuration Server Proxy. (MFWK-16897 [MFWK-16164])


Top of Page


Release Number 8.1.300.24 [04/24/15] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


To improve the migration process, you can now update the configuration options of a primary and backup pair of Configuration Servers. Previously, you had to unlink the two servers before you could update the options. (MFWK-16580)


Configuration Server now generates the following error message when attempting to add a backup T-Server to the properties of the Switch:

SCEE012 - An additional action is required to complete the requested task.

Previously, changes to the Switch list of the backup T-Server were not replicated to the primary T-Server, so the two lists maintained by the respective T-Servers became unsynchronized.

(MFWK-16386)


Top of Page


Release Number 8.1.300.23 [04/24/15] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction or modification:


Configuration Server no longer shuts down immediately after completing initialization. Previously, in release 8.1.300.22, Configuration Server finished initializing and then shut down unexpectedly. (MFWK-16627)


Top of Page


Release Number 8.1.300.22 [02/18/15] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:


Configuration Server now reports the proper number of connected clients in its log and properly releases memory when it denies authorization to a client trying to connect. Previously in this scenario, Configuration Server reported the incorrect number of connected clients in its log and did not release memory, leading to a degradation in its performance.

This problem occurred starting in Configuration Server 8.1.300.09.

(MFWK-16529)


Top of Page


Release Number 8.1.300.21 [02/06/15] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of Configuration Server.

Corrections and Modifications

This release also includes the following corrections and modifications:


In an HA configuration, if both the primary and backup Configuration Server start up at the same time, the server that originally was in backup mode and switched to primary mode now performs all configuration data updates. Previously in this scenario, that server sometimes failed to perform some configuration updates. Configuration Server logged the resulting errors as database transaction failures because of duplicate values of primary keys in the cfg_hdb_object table. (MFWK-16478 [MFWK-16404])


Configuration Server no longer terminates unexpectedly while externally authenticating a person with authentication parameters configured in the User object. (MFWK-16432 [MFWK-16292])


Top of Page


Release Number 8.1.300.19 [12/05/14] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:


When authentication fails, both the master Configuration Server and Configuration Server Proxy close the tcp connection, enabling new clients to connect to the master server. Previously, Configuration Server Proxy did not close its tcp connection, and after repeated authentication failures, the number of available tcp connections available for the process was exhausted, meaning that new clients could not connect.(MFWK-16354 [MFWK-15316])


If you delete all content in a section of the annex of a configuration object and add new content to that section in the same operation, Configuration Server now retains that section in the database and stores the new content in that section. Previously in this scenario, Configuration Server removed the section from the database and stored the new content without a related section. The problem did not become evident until Configuration Server was restarted, when the section and the new content was not displayed in the annex. (MFWK-16194)


Top of Page


Release Number 8.1.300.18 [07/11/14] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction or modification:


Configuration Server now maintains the integrity of Virtual Agent Groups (VAGs) if, during startup, a backup Configuration Server loses its connection to the primary Configuration Server before it completes data retrieval. Previously in this scenario, when the backup Configuration Server switched to primary, it did not calculate the VAGs. (MFWK-15822)


Top of Page


Release Number 8.1.300.17 [05/14/14] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:


If an application changes the value of certain configuration object fields, such as Reset Password to the special value Unknown, Configuration Server now notifies its clients about these changes. Likewise, after a Configuration Server switchover, these changes appear to have been lost (previous values are returned) until the Configuration Servers are restarted. Previously in these scenarios, clients were not notified about these changes, sometimes resulting in unexpected error messages. (MFWK-15740)


Configuration Server Proxy now handles expired passwords and their subsequent resets properly. Previously, users who had changed their password after expiration were still prompted to change their passwords when logging in to applications through Configuration Server Proxy. (MFWK-15739 [MFWK-15673])


Configuration Server now sends correct notifications of a password change by an agent that does not change the user's status as an agent. Previously, when an agent changed his or her password because the Reset Password flag had been set, Configuration Server sent incorrect notifications to its clients that the Person object no longer represented an agent. (MFWK-15490 [MFWK-15466])


Configuration Server correctly propagates new permissions to the child objects contained in a folder when permissions are changed on that folder so that the new permissions coincide with the permissions on its parent object. Previously, newly applied permissions were propagated in the database, but not in the in-memory image of the child objects. The resulting discrepancy between the in-memory permissions and the permissions stored in the database caused database-level errors upon subsequent attempts to change permissions on the contained objects. (MFWK-15393 [MFWK-14962])


Top of Page


Release Number 8.1.300.16 [12/03/13] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:


Master Configuration Server no longer sends incorrect notifications on password reset if a folder containing Person objects is disabled and later enabled. Previously in this scenario, the master Configuration Server sent incorrect notifications about a password reset for the objects contained in the folder, which prevented users from logging in to Configuration Server Proxy until it was restarted. (MFWK-15175)


Configuration Server now correctly stores role privileges in the Role objects after the privileges have been modified. Previously, modified privileges were lost when Configuration Server was restarted. (MFWK-15158)


This version addresses incompatibility of the protocol/schema versions between Configuration Server 8.1.3 and Configuration Server Proxy 8.0.3. Previously, Configuration Server Proxy 8.0.3 connected to a master Configuration Server 8.1.3 failed to read Person objects because of the incompatibility of protocol/schema versions. To run Configuration Server 8.0.3 Proxies with Configuration Server 8.1.3, you must set force-md5 to true on the master Configuration Server.

Note: Different families of Configuration Server and Configuration Server Proxy have limited support during upgrade activities. Refer to the Genesys Migration Guide for more information.

(MFWK-14849)


Top of Page


Release Number 8.1.300.14 [09/10/13] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction or modification:


Configuration Server no longer drops responses to external authentication requests that come from the same client within a very short time span. Previously, Configuration Server dropped the response to an authentication request if the next request from the same client arrived before the external authentication server had responded to the previous request. (MFWK-14853)


Top of Page


Release Number 8.1.300.12 [08/08/13] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


Backup Configuration Server Proxy now correctly switches into primary mode in the following scenario:

  1. Your configuration includes redundant Configuration Server Proxies.
  2. Clients are connected to the master proxy servers.
  3. You either stop the primary Configuration Server Proxy (such as from Solution Control Interface) or a client disconnects from the primary server.

Previously in this scenario, the backup Configuration Server Proxy sometimes terminated unexpectedly.

(MFWK-14671)


If the master Configuration Server or Configuration Server Proxy is configured to use external authentication, it no longer terminates unexpectedly if multiple clients are reconnecting while the server is re-reading configuration data. Previously in this scenario, the server sometimes terminated unexpectedly. (MFWK-14133, ER# 323843852)


When a SOAP client disconnects, Configuration Server now properly decrements the session counter for the account on behalf of which the client was connected. Previously, the session counter was not decremented, which had the potential to prevent a user with a limited number of connections to Configuration Server to connect new client applications.

To provide backward compatibility, Configuration Server now also properly removes key-value (KV) pairs, as requested by the following code sample:

<userProperties action="delete">
  <list_pair key="sample_folder">
    <str_pair
      key="sample_key"
      value=""/>
  </list_pair>
</userProperties>

This sample requests that the sample_key KV pair be removed from the sample_folder list.

Previously, SOAP requests like this contained an unrelated issue that when fixed, caused Configuration Server to reject the requests containing the above data because the requests were effectively self-contradictory and incorrect. This fix restores the original behavior of removing the KV pair without rejecting the request.

(MFWK-14041, ER# 321696028)


Top of Page


Release Number 8.1.300.09 [07/03/13] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of Configuration Server.

Corrections and Modifications

This release also includes the following corrections and modifications:


When the master Configuration Server is configured in an HA pair, Configuration Server Proxy no longer disables ADDP on its connection to the master Configuration Server during switchover. Previously, Configuration Server Proxy disabled ADDP on its connection to the master Configuration Server after two consecutive session restorations to the alternating instances of the master Configuration Server HA pair. (MFWK-15728)


Configuration Server no longer terminates unexpectedly or uses 100% of the CPU after processing an authentication request for a user with individual authentication settings configured in the gauth_ldap or gauth_ldap_<n> sections of the user's Person object. Previously in this scenario, Configuration Server sometimes terminated unexpectedly or used 100% of the CPU when first attempting to authenticate the user after Configuration Server startup, or after authentication options were modified. (MFWK-14132, ER# 323843608)


Configuration Server Proxy no longer processes an authentication request with no (an empty) password if the allow-empty-password or allow-external-empty-password option is set to false. Previously, Configuration Server Proxy ignored the value of these options and processed (either internally or by forwarding the request, as configured) all authentication requests, even those with empty passwords. (MFWK-14126, ER# 323703041)


After Configuration Server and Configuration DB Server switchovers, the backup Configuration Server no longer terminates unexpectedly after connecting to the backup DB Server. This problem occurred only in release 8.1.200.24 of Configuration Server. (MFWK-14034, ER# 321550103)


On AIX platforms, Configuration Server compiled for 32-bit platforms now support up to 3.25 GB of heap memory. Previously, it supported only up to 1 GB of heap memory.

Genesys confirms that recommendations made by IBM are valid for earlier versions of Configuration Server. You can convert 32-bit AIX binaries of these earlier releases to use 3.25 GB of heap memory by using the following command:

/usr/ccs/bin/ldedit -bmaxdata:0xD0000000/dsa confserv_32

In addition, to enable the use of up to 3.25 GB of heap memory by Configuration Server, make sure that the confserv_32 process is started under a user account with appropriate ulimit -d settings.

(MFWK-13937, ER# 318629003)


If Configuration Server Proxy is configured to forward authentication requests to the master Configuration Server, but the master is unavailable, the proxy server now generates the following error message:

Authentication failed: Configuration Server Proxy is currently disconnected from the Master Configuration Server.

Previously in this scenario, the authentication requests timed out and the users' attempts to log in were unsuccessful.

(MFWK-13578, ER# 304582352)


Configuration Server Proxy or backup Configuration Server now properly opens its listening ports when fully synchronized with its respective master or primary Configuration Server, in the following scenario:

  1. Configuration Server Proxy or backup Configuration Server gets disconnected from its master Configuration Server.
  2. Shortly after the original connection is restored, but while the Proxy or backup Configuration Server is synchronizing the data with the master Configuration Server, another disconnection occurs, because of another network issue or an Advanced Disconnect Detection Protocol (ADDP) timeout.

Previously in this scenario, Configuration Server Proxy or the backup Configuration Server was sometimes prevented from opening its listening ports after it became fully synchronized with the master Configuration Server.

(MFWK-14132, ER# 260146047)


A primary Configuration Server no longer goes into Read-only mode after a second switchover, that is, when the following occurs:

  1. A switchover occurs, and the backup Configuration Server switches to primary mode.
  2. The primary Configuration Server comes back into service.
  3. Another switchover occurs—the backup Configuration Server switches back to backup mode, and the primary Configuration Server returns on-line in primary mode.

Previously, the primary Configuration switched to primary mode, but in Read-only mode, so clients were unable to connect. (MFWK-12146, ER# 250989401)


Top of Page


Release Number 8.1.200.26 [02/10/14] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction or modification:


Configuration Server now sends correct notifications to its clients when an agent is forced to change his or her password because the Reset Password flag was set. Previously in this scenario, the incorrect notification sent by Configuration Server sometimes caused some clients (such as Universal Routing Server) to assume that the Person object represented a non-agent, not an agent. (MFWK-15491)


Top of Page


Release Number 8.1.200.25 [07/05/13] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


After Configuration Server and Configuration DB Server switchovers, the backup Configuration Server no longer terminates unexpectedly after connecting to the backup DB Server. This problem occurred only in release 8.1.200.24 of Configuration Server. (MFWK-14500 [MFWK-14034, ER# 321550103])


Configuration Server Proxy no longer processes an authentication request with no (an empty) password if the allow-empty-password or allow-external-empty-password option is set to false. Previously, Configuration Server Proxy ignored the value of these options and processed (either internally or by forwarding the request, as configured) all authentication requests, even those with empty passwords. (MFWK-14159, ER# 324367845 [MFWK-14126, ER# 323703041])


Configuration Server no longer terminates unexpectedly or uses 100% of the CPU after processing an authentication request for a user with individual authentication settings configured in the gauth_ldap or gauth_ldap_<n> sections of the user's Person object. Previously in this scenario, Configuration Server sometimes terminated unexpectedly or used 100% of the CPU when first attempting to authenticate the user after Configuration Server startup, or after authentication options were modified.(MFWK-14158, ER# 324367716 [MFWK-14132, ER# 323843608])


Top of Page


Release Number 8.1.200.24 [04/08/13] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This release does not contain new features or functionality.

Note: Following the initial Hot Fix release of this version of Configuration Server on the AIX, Linux, and Windows platforms, Configuration Server 8.1.200.24 was tested on the HP-UX PA, HP-UX IPF, and Solaris platforms. On April 22, 2013, the release type for all platforms changed from Hot Fix to General.

Corrections and Modifications

This release includes the following corrections and modifications:


The backup Configuration Server is now properly promoted to primary Configuration Server after the ADDP timeout expires. Previously, this promotion did not always occur and the backup Configuration Server stayed in backup mode.

To ensure that this promotion always occurs, set the new option peer-switchover-tmout to at least twice the value of the ADDP timeout. Set this option in the configuration files of both the primary and backup Configuration Servers.

[confserv] (of the configuration file)
peer-switchover-tmout
Default Value: 30 (seconds)
Valid Values: Any integer value
Changes Take Effect: After restart

Specifies the time interval (in seconds) during which the backup Configuration Server, after receiving the command to switch to primary mode, waits for the former primary Configuration Server to complete shutdown or switchover to backup mode, and close its connection with its backup. If after expiration of this timeout, the backup server still continues to detect the primary server operating in primary mode or maintaining connection to the backup, the backup Configuration Server cancels its switchover to primary mode and continues to operate in backup mode.

To ensure reliable switchover, enable ADDP on the connection between the primary and backup Configuration Servers and make sure that this option is set to a value at least twice the ADDP timeout on that connection.

(MFWK-14026, ER# 321419174)


During switchover, the backup Configuration Server now successfully switches to primary mode when the primary DB Server is unavailable. Previously in this scenario, the backup Configuration Server failed to fully complete the switchover and remained in backup mode.

Note: This problem was introduced in release 8.1.200.22.

(ER# 319774591)


After switching to primary mode, Configuration Server now reads the current values from the cfg_max_dbid table, enabling it to properly create new objects and add annex entries to existing objects as requested. Previously, after switchover, Configuration Server was sometimes unable to make these changes because it did not retrieve the latest values from the table. This sometimes also affected the Configuration Database, causing the problems to persist even after a Configuration Server restart.

Note: This problem was introduced in release 8.1.200.22.

(ER# 319344692)


Configuration Server now continues running immediately after a client application disconnects. Previously in this scenario, Configuration Server would sometimes terminate unexpectedly.

Note: This problem was introduced in release 8.1.200.22.

(ER# 319155422)


Configuration Server now provides a new option to temporarily restore behavior that existed in Configuration Server prior to 8.1.2. In these previous releases:

This old behavior was a lapse in security, enabling users to assume permissions on configuration objects for which they were not originally granted, by moving objects between folders.

In Configuration Server 8.1.2, this behavior was modified so that a user must have the permissions explicitly granted to him or her to be able to perform these actions. The new option enable-pre-812-security provides the means to temporarily restore the old behavior until the desired security configuration can be achieved by explicitly granting the required permissions to only those users or access groups who are intended to be authorized to move the objects, as described above. This option should be used only in exceptional cases, and only as a temporary measure. Note that the new 8.1.2 behavior, which provides the proper security, remains the default behavior.

To enable this, set the following new option enable-pre-812-security to true in the confserv section of the primary master Configuration Server, and in the corresponding main section of the backup master Configuration Server:

enable-pre-812-security
Default Value: false
Valid Values: false, true
Changes Take Effect: Immediately

If set to true, this option restores pre-8.1.2 security behavior, as follows:

If set to false (the default), both actions are disabled.

To take effect, this option must be set to true in both the confserv section of the primary master Configuration Server, and in the corresponding main section of the backup master Configuration Server.

(ER# 317083824)


Top of Page


Release Number 8.1.200.22 [02/21/13] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Please be advised that, because of a severe issue found in this release of Configuration Server, it has been removed from the Software Download site and is not available by request. For detailed information about this issue, refer to the Product Advisory.

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


Configuration Server Proxy or a backup Configuration Server no longer terminates unexpectedly when starting if it receives unsolicited notifications about object updates before initial data retrieval is complete. Previously in this scenario, Configuration Server, running in Proxy or backup mode would sometimes terminate during startup. (ER# 316674064)


In the following scenario:

  1. Configuration Server Proxy is connected to the primary Configuration Server.
  2. The primary Configuration Server shuts down and the backup Configuration Server switches over to run in primary mode.
  3. Configuration Server Proxy attempts to connect to the backup Configuration Server running in primary mode.
  4. The original primary Configuration Server is restarted, and the backup Configuration Server switches back to running in backup mode.

Configuration Server Proxy now properly attempts to connect to the restarted primary Configuration Server. Previously, it kept trying to connect only to the backup Configuration Server. (ER# 315781298)


When a client uses the MSGCFG_ADDOBJECT message to add a new configuration object through a writable Configuration Server Proxy, all clients of the server are now notified. Previously in this scenario, Configuration Server Proxy did not send notifications to clients registered on behalf of accounts other than default. (ER# 315337199)


This version of Configuration Server improves the stability of failover between primary and backup instances. Backup Configuration Server no longer commits an unexpected switchover if the primary Configuration Server is still running. Instances of Configuration Server in a high-availability (HA) configuration no longer exit if they see their peer server in an unexpected state; instead, they make sure that read-only mode is set on affected servers until the collision is resolved. (ER# 314154959)


On the Linux platform, CPU utilization of Configuration Server no longer reaches 100% if the number of connected clients reaches the number of socket descriptors allocated for the Configuration Server process. Previously in this situation, this process used 100% of the CPU. However, this excessive usage did not affect the ability of Configuration Server to handle existing clients. (ER# 308443003)


In the following scenario:

  1. The primary Configuration Server stops.
  2. The backup Configuration Server receives the signal to switch over to primary mode. It detects the loss of data concurrency and initiates data reload.
  3. Before the data reload is completed, the primary Configuration Server is restarted.
  4. The primary Configuration Server is unable to detect the backup Configuration Server preparing to run in primary mode because it is still reloading the data and has not yet completed the switchover to primary mode yet. As a result, the restarted primary Configuration Server starts to run in primary mode by itself.
  5. Through the collision prevention mechanism, the backup Configuration Server, detects the other Configuration Server and tries to connect to it. However, the connection attempt fails because the restarted primary Configuration Server server is not completely initialized.

The backup Configuration Server now remains in primary Read-Only mode until its HA peer completes the switchover. Previously in this scenario, the backup Configuration Server would just terminate normally.

(ER# 308195371)


When using LDAP external authentication, you can now configure secure connections to LDAP servers that use security certificates from different certificate authorities (CA). To use this new functionality, set the [gauth-ldap] cacert-path options in multiple locations (on Server, Tenant, or User level) to point to different CA certificates.

Previously, Configuration Server did not support secure connections to remote LDAP servers that were authenticated by certificates issues by different CAs.

(ER# 303319430)


Top of Page


Release Number 8.1.200.18 [12/07/12] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction or modification:


When Configuration Server Proxy is configured to send authentication requests directly to LDAP or RADIUS servers, Configuration Server Proxy can now reject empty passwords in client connections by setting the allow-external-empty-password configuration option to false in the csproxy section of its Application object. Previously in this scenario, Configuration Server Proxy would not reject empty passwords. (ER# 313575550)


Top of Page


Release Number 8.1.200.17 [11/21/12] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of Configuration Server.

Corrections and Modifications

This release also includes the following corrections and modifications:


It is no longer possible for a user, who does not have Change permission on a folder, to move objects from that folder to another location. Likewise, it is no longer possible for a user, who does not have Change Permissions permission on an object, to change the object's permissions implicitly by moving the object with inherited permissions between folders with different permissions. Previously, both of these actions were possible under the conditions described above. (ER# 309382847)


Configuration Server no longer terminates unexpectedly when processing a request to assign a value containing more than 509 characters to a string property of an object. Previously in this scenario, Configuration Server would generate an error message as required, but its memory would sometimes be corrupted, causing Configuration Server to terminate unexpectedly. (ER# 309292608)


Configuration Server now allows you to delete User and Access Group objects to which Roles are assigned. Previously, an attempt to do so was rejected and the Dependent objects error message generated.

Note: Genesys recommends that you assign Roles to Access Groups and assign Users to those Access Groups, instead of assigning Roles to Users directly.

(ER# 308797966)


Configuration Server Proxy now correctly handles password changes for Person objects that existed before Configuration Server was upgraded to release 8.1.1. Previously, passwords of those pre-existing accounts that were changed after the upgrade to 8.1.1 could not be used to log in to Configuration Server Proxy until Configuration Server Proxy was restarted. (ER# 307988371)


Client sessions are now properly restored after a master Configuration Switchover. Previously, the sessions were not restored after the switchover, causing clients to have to reread the entire configuration. (ER# 304076036)


Configuration Server no longer logs the error Message hasn't been created. Previously this confusing message was logged when a notification is not cached for delivery to multiple clients. Its appearance in the log did not indicate any problem in functionality. (ER# 303724855)


External authentication using LDAP now works correctly if Configuration Server or Configuration Server Proxy is configured for server-only authentication, that is, when the cacert-path option is configured and the key-path option is omitted. Previously, Configuration Server did not recognize the security certificate and the authentication attempt failed. (ER# 302797950)


If a request is received by Configuration Server Proxy to disable a Tenant or Person folder, and if the Tenant contains one or more Person objects, the folder is disabled as requested and the status of the contents of the folder are now changed to Disabled. Previously in this scenario, the contents of the folder remained with a status of Enabled. (ER# 299422871)


When rejecting write requests from a server application that is connected on behalf of the SYSTEM account, Configuration Server now returns an error with the correct message Insufficient permissions to complete this operation.

Previously in this scenario, Configuration Server returned an error with the incorrect reason of Configuration Server operating in emergency mode.

(ER# 289231875)


When an object or a folder that has its own Access Control List (as opposed to permissions propagated from the parent) is moved from a folder, to which a user does not have Read access, to a folder to which that user does have Read access, permissions to that object do not change because they are defined by the object's own Access Control List. Previously in this scenario, Configuration Server incorrectly sent the MSGCFG_OBJECTADDED notification to the client connected on behalf of that user, giving the impression that the permissions had been changed. (ER# 287470231)


Configuration Server Proxy now continues to function properly in the following scenario:

  1. The connection to the master Configuration Server is lost because of Automatic Disconnect Detection Protocol (ADDP) timeout expiration, or because of network failure.
  2. Configuration Server Proxy tries to restore the connection to the master Configuration Server, which is temporarily not responding while it is performing a lengthy atomic operation (see related ER# 306332231)

Configuration Server Proxy continues to operate in read-only mode and correctly handle its clients' requests (including processing ADDP packets), while waiting for the master Configuration Server to respond.

Previously in this scenario, Configuration Server Proxy itself became unresponsive, and remained so until the master Configuration Server completed its lengthy operation and accepted the connection with Configuration Server Proxy. This in turn sometimes caused clients of Configuration Server Proxy to incorrectly detect that Configuration Server Proxy had disconnected because of ADDP timeout expiration, and they then initiated the reconnect procedure to Configuration Server Proxy.

(ER# 283555276)


Configuration Server no longer terminates unexpectedly with the unhandled exception STATUS_RESOURCE_NOT_OWNED (ExceptionCode: 0xc0000264) after processing 0x7fffffff (2147483647 in decimal) requests. (ER# 280749927)


On Solaris platforms, Configuration Server now correctly transcodes national characters during an XML import or export. Previously, some non-ASCII were sometimes not converted correctly.

To enable this correction (on Solaris platforms only), before starting Configuration Server, set the new environment variable GCTI_TRANSLOCALCP to the name of the local code page, as contained in the list returned by the iconv -l command.

(ER# 280100615)


After a switchover, the primary Configuration Server now reports the correct number of GUI clients in the logs (the Number of GUI clients: value). Previously, the incorrect number was sometimes reported. (ER# 274197511)


If master Configuration Server switchover occurs while a new Tenant is being created on Configuration Server Proxy, the new Tenant now appears in Configuration Manager. (ER# 272353802)


Duplicate instances of the same object created through a writable Configuration Server Proxy are no longer displayed by a client connected to Configuration Server Proxy after the master Configuration Server has switched over to its backup. (ER# 268804508)


Last Login information is now synchronized between the master Configuration Server and Configuration Server Proxies. For example, if a user logs into the master Configuration Server, then logs into a Configuration Server Proxy, the Last Login information displayed the second time reflects the login attempt to the master Configuration Server. Previously in this example, the Last Login information displayed for the second login reflected the last login attempt to that Configuration Server Proxy. (ER# 241981648)


Top of Page


Release Number 8.1.100.18 [10/17/12] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction or modification:


Configuration Server Proxy now correctly handles password changes for Person objects that existed before Configuration Server was upgraded to release 8.1.1. Previously, passwords of those pre-existing accounts that were changed after the upgrade to 8.1.1 could not be used to log in to Configuration Server Proxy until Configuration Server Proxy was restarted. (ER# 310752925 [307988371])


Top of Page


Release Number 8.1.100.17 [09/11/12] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


Configuration Server Proxy now properly updates the list of agents in a Virtual Agent Group that was changed by a client of that Configuration Server Proxy by changing the Virtual Agent Script. Previously, the list of agents was calculated correctly on the master Configuration Server, but not updated on the Configuration Server Proxy through which the request was forwarded. (ER# 307505001 [304906112])


This version fixes a memory leak that sometimes occurred if LDAP external authentication was used and the option ldap-url was configured in Person objects. (ER# 306536961)


Configuration Server now correctly handles SOAP requests that contain XML entities such as &apos;. Previously, requests containing this and similar XML entities were handled either incorrectly or not at all. (ER# 305818435)


Writable Configuration Server Proxy now properly updates the record with an empty string ("") when requested by a client through a SOAP port. Previously in this scenario, a request such as this was not committed to the records maintained by Configuration Server Proxy, leaving the record set to its previous value. However, the request was forwarded to the master Configuration Server, which did store the empty string. (ER# 305549120 [303319290])


In redundant Configuration Server environments, Virtual Agent Groups are now handled properly, and their functionality preserved, if a real or perceived loss of data concurrency is detected during a switchover between the primary and backup Configuration Servers. Previously, the switchover of a backup server to primary mode, if a loss of data concurrency was detected, would cause the Virtual Agent Groups to become dysfunctional, not updating properly. (ER# 305430948 [301075007])


External authentication using LDAP now works correctly if Configuration Server or Configuration Server Proxy is configured for server-only authentication, that is, when the cacert-path option is configured and the key-path option is omitted. Previously, Configuration Server did not recognize the security certificate and the authentication attempt failed. (ER# 304501688 [302797950])


Configuration Server no longer terminates unexpectedly with the unhandled exception STATUS_RESOURCE_NOT_OWNED (ExceptionCode: 0xc0000264) after processing 0x7fffffff (2147483647 in decimal) requests. (ER# 303830631 [280749927])


Top of Page


Release Number 8.1.100.16 [06/25/12] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:


Configuration Server now allows a Dialing Filter to be created using Genesys Administrator if the length of the string in the conditions exceeds 255 characters. (ER# 300793695 [299219094])


Top of Page


Release Number 8.1.100.15 [05/25/12] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:


Configuration Server running as a backup, Proxy, or Proxy backup server now properly processes notifications from the primary Master server about object creation in a subfolder when the dbIDs of the two entities are identical. Previously in this scenario, Configuration Server running as a backup, Proxy, or Proxy backup server sometimes either produced a core file and terminated unexpectedly (immediately or shortly thereafter), or the subfolder disappeared from Configuration Server Proxy data. (ER# 299888531, 297879796, 298358682)


Top of Page


Release Number 8.1.100.14 [05/22/12] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:


Configuration Server no longer terminates unexpectedly when using LDAP external authentication. Previously, if the response from the LDAP Server contained an escape sequence such as %s, and if the option verbose was set to its maximum value, Configuration Server terminated. (ER# 297804721, 296915383)


Configuration Server no longer terminates unexpectedly if the connection to the LDAP server is lost during request processing. (ER# 289761437)


Top of Page


Release Number 8.1.100.12 [04/17/12] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:


Configuration Server Proxy no longer terminates unexpectedly while it is processing notifications from the master Configuration Server for the deletion of Tenants that contained users (Person objects). (ER# 298062856)


Top of Page


Release Number 8.1.100.11 [04/06/12] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of Configuration Server.

Corrections and Modifications

This release includes the following corrections and modifications:


If password validation rules (introduced in Configuration Server 8.0.300.49) are enabled for a Tenant, newly created Person objects created under that now always appear in their respective folders after a Configuration Server restart. Previously in this scenario, the newly-created Person objects did not appear in their respective folders, although they could be found using Search functionality. (ER# 297264865, 295432928)


Configuration Server now sends complete and correct notifications of object creation and modification to clients which had subscribed without the exclude_bytecode restriction, enabling Universal Routing Server (URS) to read newly created or updated routing strategies. Previously, these notifications were missing the bytecode binary Annex attributes. As a result, URS could not read newly created or updated routing strategies.

This problem, which was introduced in Configuration Server 8.1.000.14, appeared intermittently, depending on the order in which different clients connected to Configuration Server.

(ER# 296090372, 286218181)


Configuration Server Proxy no longer terminates when the connection to the master Configuration Server is lost while retrieving data from the master Configuration Server. (ER# 291904580)


You can now update Voice Platform Profile configuration objects through Configuration Server Proxy. (ER# 289967249)


Case-insensitive searches in Configuration Server now function properly, even if wildcards are used. Previously in this scenario, the search mechanism sometimes returned a case-sensitive search result. For example, a case-insensitive search for *BC* now returns ABCD and abcd. Previously, this search returned only ABCD. (ER# 297317971, 284247665)


The LCA port can now be configured at a value greater than 9999. Previously, the port number had to be set to 9999 or less. (ER# 283620749)


A PSDK client no longer gets the MissingAttributeException error when receiving the EventObjectUpdated message from Configuration Server. (ER# 283616803)


Configuration Server now includes sent to information in logs when changes are made in the Configuration Database. Previously, in this scenario, this information was not included in logs and made troubleshooting very difficult. (ER# 283511811)


The master Configuration Server now reports its exact version number in the Version field of its Application object. Previously, this field contained only the major version number that was entered during database initialization. (ER# 270651528)


Upper limits on the values of History Log options max-records, expiration, and client-expiration have been removed. However, the greater the number of History Log records kept by Configuration Server above these options' default values might significantly reduce the performance of Configuration Server and increase its memory consumption. (ER# 257652591)


The backup Configuration Server now switches over to primary mode correctly, even if it has log options configured in both the Application object and its local configuration file. Previously, you had to configure log options in only the configuration file, not in the Application object for correct switchover. (ER# 156491260)


Top of Page


Release Number 8.1.000.19 [06/14/12] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In several scenarios involving Configuration Server configured for external authentication using LDAP, memory leaks and unexpected terminations were identified and fixed. (ER# 300975863 [298532351], 300929515 [289761437], 296915383 [297804721], 295417154, 287592029)


When using LDAP external authentication, if the option allow-empty-password is set to true, Configuration Server no longer passes authentication requests with empty (blank) passwords to the LDAP server if the option allow-external-empty-password is set to false. Previously, Configuration Server ignored the value of allow-external-empty-password, and passed the authentication requests with the blank password. (ER# 300842049 [296487805])


Configuration Server running as a backup, Proxy, or Proxy backup server now properly processes notifications from the primary Master server about object creation in a subfolder when the dbIDs of the two entities are identical. Previously in this scenario, Configuration Server running as a backup, Proxy, or Proxy backup server sometimes either produced a core file and terminated unexpectedly (immediately or shortly thereafter), or the subfolder disappeared from Configuration Server Proxy data. (ER# 300462800 [299888531, 298358682, 297879796])


Configuration Server now allows a Dialing Filter to be created using Genesys Administrator if the length of the string in the conditions exceeds 255 characters. (ER# 299219094)


Case-insensitive searches in Configuration Server now function properly, even if wildcards are used. Previously in this scenario, the search mechanism sometimes returned a case-sensitive search result. For example, a case-insensitive search for *BC* now returns ABCD and abcd. Previously, this search returned only ABCD. (ER# 297317973 [284247665])


Top of Page


Release Number 8.1.000.18 [04/13/12] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


Configuration Server Proxy no longer terminates when the connection to the master Configuration Server is lost while retrieving data from the master Configuration Server. (ER# 284356401, 288453370)


Configuration Server now sends complete and correct notifications of object creation and modification to clients which had subscribed without the exclude_bytecode restriction, enabling Universal Routing Server (URS) to read newly created or updated routing strategies. Previously, these notifications were missing the bytecode binary Annex attributes. As a result, URS could not read newly created or updated routing strategies.

This problem, which was introduced in Configuration Server 8.1.000.14, appeared intermittently, depending on the order in which different clients connected to Configuration Server.

(ER# 286218181)


You can now update Voice Platform Profile configuration objects through Configuration Server Proxy. (ER# 289967249)


Top of Page


Release Number 8.1.000.17 [01/27/12] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


This release eliminates the memory leak that occurred when Configuration Server sent notifications to its clients. Previously, this memory leak sometimes caused Configuration Server to terminate because of lack of memory. (ER# 287592029)


Configuration Server no longer terminates when Interactive Routing Designer (IRD) tries to connect. Previously, Configuration Server would sometimes terminate unexpectedly when IRD tried to establish a connection with Configuration Server. (ER# 287910671, 284114553)


Configuration Server now uses a new algorithm when it prepares messages to be sent to client applications. Previously, when responding to a client application request, Configuration Server would sometimes report a message packing error when attempting to pack large objects configured in the Configuration Layer. (ER# 283975913, 291683931)


Top of Page


Release Number 8.1.000.16 [11/16/11] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This release does not contain new features or functionality.

Note: Following the initial Hot Fix release of this version of Configuration Server, the release type changed from Hot Fix to General on January 4, 2012.

Corrections and Modifications

This release includes the following corrections and modifications:


On the Windows 64-bit platform, Configuration Server now properly packs newly created objects, such as DNs, that contain empty lists of key-value pairs in their Annex. Previously on this platform, Configuration Server packed these objects incorrectly, which sometimes prevented client applications that used the Java Configuration Library 6.x, such as Genesys Info Mart 8.0.x, from initializing successfully at startup. (ER# 284811502)


After a restart of Configuration Server, information about the association between a T-Server Application object and a Switch object is now retained in the Configuration Database. Previously after the restart, the association was deleted from the database and replaced with a CONN_INFO section in the Annex of the T-Server object. This prevented Genesys Info Mart 8.0.x from correctly initializing the T-Server object. (ER# 284038026)


Top of Page


Release Number 8.1.000.15 [10/11/11] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:


Previous versions of Configuration Server that were configured to use both LDAP external authentication and open secure (TLS) ports used to terminate upon startup on UNIX platforms. To fix this problem, you must:

  1. On all UNIX platforms, upgrade to this version of Configuration Server.
  2. On HP-UX and Linux platforms, upgrade to Genesys Security Pack on UNIX version 8.1.000.01.

(ER# 278312655)


Top of Page


Release Number 8.1.000.14 [07/13/11] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in the initial 8.1 release of Configuration Server.

Corrections and Modifications

This release includes the following corrections and modifications that were made between release 8.0 or earlier releases and the initial 8.1 release:


When using LDAP external authentication, Configuration Server now correctly handles the situation in which a client disconnects during the authentication process and a new client connects on the same socket. Previously in this situation, an incorrect username was returned by the authentication process and the client rejected the response. (ER# 265834215)


Only users who are members of the SuperAdministrators Access Group can set Configuration Server into Emergency Mode. Previously, any user could activate Emergency Mode, regardless of their permissions. (ER# 263437191)


Configuration Server Proxy now generates correct notifications of a new object created in a subfolder of the root object. Previously, the incorrect notification described the new object as being created in the root folder, rather than in a subfolder of the root. (ER# 256930265)


After switching over to backup mode, Configuration Server Proxy now resets the Total number of clients counter that is written to the log. Previously, after the switchover, Configuration Server properly disconnected all its clients but did not reset the counter. As a result, when switched back over to primary mode, the log recorded a total number of clients value that included previously disconnected clients.

Note:This issue affected only log output. Actual functionality of Configuration Server Proxy was not affected.

(ER# 255601919)


If redundant Message Servers are configured, Configuration Server Proxy, when configured for network logging, now connects to the primary Message Server at startup as designed. Previously, Configuration Server Proxy sometimes connected to the backup Message Server, or failed to connect to any Message Server. (ER# 248683441)


Configuration Server now correctly handles a mixture of multi- and single-byte characters. Previously, mixing the two character types sometimes resulted in character strings in which characters were truncated, rearranged, or missing.(ER# 247036347)


Configuration Server now correctly processes requests to retrieve Person and Agent Group objects if the request was based on filters for either Tenant, Agent Group and State, or both. Previously, Configuration Server processed these requests incorrectly. (ER# 227924026)


The default Administrators Access Group now receives full access to all of the objects belonging to a Tenant. Previously, members of the Administrators Access Group had only Read access to the objects belonging to a Tenant. (ER# 214771000)


The speed at which Configuration Server deletes a large number of objects has been significantly improved. (ER# 185408681)


Top of Page


Documentation Corrections

This section provides corrections and updates for issues found in currently released documentation for this product. The changes described here will be included in future published versions of the document.


The Framework 8.1 Configuration Options Reference Manual contains incorrect information about the allow-empty-password and allow-external-empty-password options for Configuration Server, on page 64 as follows:

This should read as follows:


The Framework 8.1 Configuration Options Reference Manual is missing descriptions of the following two configuration options for Configuration Server Proxy that were added in 8.1, as follows:

allow-empty-password
Section: [csproxy]
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately

Specifies whether Configuration Server Proxy allows an empty (blank) password in a client connection request. If the option is set to false and the password in a request is not specified, Configuration Server Proxy rejects the request and generates a corresponding error message.

Note: The Tenant option password-min-length overrides the value of allow-empty-password for all users in the Tenant in which the latter option is configured. Genesys strongly recommends that you use password-min-length instead of allow-empty-password. The latter has been provided only for purposes of backward compatibility.

allow-external-empty-password
Section: [csproxy]
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately

This option is used only if external authentication is being used.

Specifies whether Configuration Server Proxy allows an empty (blank) password in a client connection request when these requests are authenticated externally. When set to true (default), Configuration Server Proxy will permit an unspecified password in an externally authenticated request.

Note:There might be instances where an LDAP server, instead of rejecting a blank password, might (depending on the LDAP Server configuration) interpret this to mean that it should make an unauthenticated connection, giving the false impression that authentication has succeeded. To allow empty passwords in Configuration Server Proxy and still avoid this, set the allow-empty-external-password option to false so that configuration will enforce at least one character in a password sent to an external system.

If the option is set to false and the password in a request is not specified, Configuration Server Proxy rejects the request and generates a corresponding error message, regardless of the value of the two other options.

Refer to the "User Passwords" chapter of the Genesys Security Deployment Guide for more information about these options and how to use them.


The Framework 8.1 Deployment Guide contains an incomplete description of how to modify configuration files when setting up an redundant configuration DB Servers. In the section entitled "Modifying the Configuration Files", information about modifying the Configuration Server configuration file is missing. The next published version of the Deployment Guide will contain the missing information, as follows:

The configuration file of the Configuration Server, confserv.cfg must be modified as follows:

These modifications are shown in bold in the following excerpt from a modified Configuration Server configuration file:

[dbserver]
host=123.45.678.90
port=4040
dbengine=oracle
dbserver=cs
username=cs
password=cs
server=backupdbserver
reconnect-timeout=10
reconnection-timeout=600

[backupdbserver]
host=123.45.678.90
port=4041
dbengine=oracle
dbserver=cs
username=cs
password=cs
server=
reconnect-timeout=10
reconnection-timeout=600

Note: If a backup Configuration Server is deployed, the same changes must be made in the configuration file of the backup Configuration Server.

(MFWK-14974)


The Framework 8.1 External Authentication Reference Manual contains an incorrect spelling of a configuration option on page 37, as follows:

The next published version of the Reference Manual will contain the following corrected sentence:

(MFWK-14482, ER# 313695348)


Top of Page


Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with this product.


Do not configure auto-restart for both the primary and backup Configuration Servers in a redundant pair.


If you used an older version of Genesys Administrator or Configuration Manager to create new Access Groups by copying an existing predefined Access Group (such as Administrators or EVERYONE), you might be unable to remove the new Groups through Configuration Server; you can only do this directly in the Configuration Database.

Workaround: To avoid this situation, use the latest version of Genesys Administrator available. If you have already experienced this issue and were unable to remove some Groups, please contact Genesys Technical Support for detailed instructions.


When using LDAP external authentication, Configuration Server stops authenticating users if one of the two connections that Configuration Server makes to the LDAP server is rejected while the other connection is maintained.

Workaround:To avoid this problem, make sure all LDAP servers are able to connect to Configuration Server, and set all connection expiration timeouts to their maximum values so connections, once established, can be reused as long as possible.

(MFWK-17536 [MFWK-17452])

Found In: 8.1.300.27 Fixed In: 

Configuration Server cannot process an incoming message that is in the wrong format, and will terminate unexpectedly as a result.

Workaround: To avoid this problem, do not scan Configuration Server ports, or upgrade to (by dropping in) the latest 8.5.1 version of Configuration Server.

(MFWK-18713)

Found In: 8.1.300.19 Fixed In: 8.5.101.07

If you delete all content in a section of the annex of a configuration object and add new content to that section in the same operation, Configuration Server deletes that section from the database and stores the new content without a related section. The problem does not become evident until Configuration Server is restarted, when the section and the new content is not displayed in the annex.

Workaround: To avoid this problem, always add at least one new option and save or apply that change before removing all of the old content. This ensures that the existing section is not removed from the database.

(MFWK-16194)

Found In: 8.1.300.16 Fixed In: 8.1.300.19

Configuration Server does not export Campaign objects that contain Campaign Groups into XML correctly. If Campaign Groups exist, they are stored in XML as obsolete CampaignGroupInfo entities that cannot be imported. This issue appears to have been introduced in release 7.5 and affects both import and export methods, using SOAP or the Configuration Server internal and export feature (-import and -export options) in Configuration Server. (MFWK-14427)

Found In: 8.1.300.09 Fixed In: 

Configuration Server might not properly initialize all configured features, including SOAP and external authentication, from its configuration file when starting up on a newly initialized database.

Workaround: Restart Configuration Server.

(MFWK-14507; MFWK-14171, ER# 324726008)

Found In: 8.1.300.09 Fixed In: 

If you use a tool other than Windows certificate services to generate the TLS security certificate and then import the certificate to Windows manually, the CERT_TRUST_REVOCATION_STATUS_UNKNOWN validation error will occur and the TLS connection to the Genesys server will fail.

Workaround: Set the client-auth option to 0 (zero) to disable server authentication in the client TLS socket. Refer to the Framework 8.1 Configuration Options Reference Manual for a full description of this option and how to use it.

(MFWK-14166, ER# 324547671)

Found In: 8.1.300.09 Fixed In: 

When enabled for multi-language support, Configuration Server does not support section and option names more than 256 bytes in length. (MFWK-14141, ER# 324029037)

Found In: 8.1.300.07 Fixed In: 

When enabled for multi-language support, Configuration Server does not support string values more than 256 bytes in length. (MFWK-14140, ER# 324029035)

Found In: 8.1.300.07 Fixed In: 

In an HA configuration, if you start the backup Configuration Server Proxy while the primary server's host is not available, the backup server sometimes stops responding and does not switch to primary mode.

Workaround: If this occurs, manually perform the switchover using the Solution Control Server utility mlcmd or start the primary Configuration Server Proxy.

(MFWK-16164)

Found In: 8.1.200.17 Fixed In: 

After a switchover, the primary Configuration Server may report the incorrect number of GUI clients in the logs (Number of GUI clients: value). (ER# 274197511)

Found In: 8.1.000.14 Fixed In: 8.1.200.17

If [security-authentication-rules]password-no-repeats is set to a value greater than 1 in the Tenant in which the default user resides, after a user changes the password of the default user once, Configuration Server no longer allows any changes to the default user object. The user might also disappear from the root folder after subsequent restarts of Configuration Server. Make sure you change the default password first, before you configure any password history rules in you system. (MFWK-17943)

Found In: 8.1.100.11 Fixed In: 

If a request is received by Configuration Server Proxy to disable Tenant or Person folder, and if the Tenant contains one or more Person objects, the folder is disabled as requested, but the contents of the folder remain with a status of Enabled. (ER# 299422871, 271201450)

Found In: 8.1.000.11 Fixed In: 8.1.200.17

When configuring multiple LDAP servers for User or Tenant objects, the value of the password parameter for all but the first server is not hidden or masked in the annex of the object.

Workaround: Use the new LDAP Server configuration options and structure introduced in release 8.1.1, in which the password field is masked automatically and therefore is not visible in the annex of the object.

(MFWK-14031, ER# 321549513)

Found In: 8.0.300.58 Fixed In: 8.1.100.14

If password validation rules are enabled for a Tenant, newly-created Person objects created in that Tenant might, in rare cases, not appear in their respective folder after a Configuration Server restart.

Workaround: Use the Search functionality to find these objects.

(ER# 295432928)

Found In: 8.0.300.49 Fixed In: 8.1.100.11

When attempting to edit configuration objects from a server application that:

Configuration Server rejects any write requests and returns an error message with the incorrect reason of Configuration Server operating in emergency mode instead of the correct reason of Insufficient permissions to complete this operation.

Workaround: To avoid this message, make sure you are running all applications that require write access with using appropriate accounts with appropriate and sufficient permissions.

(ER# 289231875)

Found In: 8.0.300.49 Fixed In: 8.1.200.17

If master Configuration Server switchover occurs while a new Tenant is being created on Configuration Server Proxy, the new Tenant does not appear in Configuration Manager. (ER# 272353802)

Found In: 8.0.300.42 Fixed In: 8.1.200.17

When the master Configuration Server changes Configuration Server Proxy to Read-only or Emergency Mode, Configuration Server Proxy does not notify its clients of the change in mode. (MFWK-12564, ER# 269933185)

Found In: 8.0.300.42 Fixed In: 

Duplicated instances of the same object created through a writable Configuration Server Proxy are displayed by a client connected to Configuration Server Proxy after the master Configuration Server has switched over to its backup. (ER# 268804508)

Found In: 8.0.300.42 Fixed In: 8.1.200.17

When a Configuration Server performs a lengthy atomic operation (for example, removing an object with many subordinate objects or serving a large portion of the history log to a client), it may not respond promptly to Advanced Disconnect Detection Protocol (ADDP). As a result, clients with ADDP timeouts set to smaller values may experience a disconnect.

Workaround: To avoid this from occurring, if ADDP is enabled, set the ADDP timeout to accommodate the performance of Configuration Server on the particular platform. As a general rule, set the ADDP timeout on connections to Configuration Server for all Configuration Server clients to at least 60 seconds.

(MFWK-13637, ER# 306332231)

Found In: 8.0.300.30 Fixed In: 

In the following scenario:

  1. Configuration Server Proxy or backup Configuration Server gets disconnected from its master Configuration Server.
  2. Shortly after the original connection is restored, but while the Proxy or backup Configuration Server is synchronizing the data with the master Configuration Server, another disconnection occurs, because of another network issue or an Advanced Disconnect Detection Protocol (ADDP) timeout.

Configuration Server Proxy or backup Configuration Server might be prevented from opening its listening ports when it is fully synchronized with the master Configuration Server.

Workaround: If your environment experiences a series of successful connection attempts, followed shortly after by disconnects, without the connecting Configuration Servers reporting they are fully initialized, Genesys recommends that you shut down the affected components, resolve the connectivity issue and/or adjust the ADDP configuration on the master Configuration Server, and then restart the components to ensure that they can initialize properly. As a general rule, set the ADDP timeout on connections to Configuration Server for all Configuration Server clients to at least 60 seconds.

(MFWK-12350, ER# 260146047)

Found In: 8.0.300.27 Fixed In: 8.1.300.09

Last Login information is not synchronized between the master Configuration Server and Configuration Server Proxies. For example, if a user logs into the master Configuration Server, then logs into a Configuration Server Proxy, the Last Login information displayed the second time does not reflect the login attempt to the master Configuration Server, but only the last login attempt to that Configuration Server Proxy.

Workaround: To avoid this, Genesys recommends that users always log in through the same Configuration Server (master or Proxy).

(ER# 241981648)

Found In: 8.0.200.09 Fixed In: 8.1.200.17

Tenant names must not contain one or more backslash characters (\). (MFWK-11598, ER# 229940114)

Found In: 8.0.100.18 Fixed In: 

Configuration Server in Proxy mode cannot be deployed using the Web Deployment Tool in Genesys Administrator. Use the manual deployment process described in the Framework 8.1 Deployment Guide instead. (MFWK-11012, ER# 193827147)

Found In: 8.0.000.09 Fixed In: 

If the backup Configuration Server has log options configured the same in both the Application object and in its local configuration file, it may not switch over to Primary mode correctly when required.

Workaround: Configure log options in the configuration file, not in the Application object.

(ER# 156491260)

Found In: 7.6.000.04 Fixed In: 8.1.100.11

Top of Page


Discontinued Support

This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list. For more information on discontinued support for operating environments and databases, see "Discontinued Support" in the Genesys Supported Operating Environment Reference Guide.


HP Compaq Tru64 Alpha is no longer supported.

Discontinued As Of: 8.1.000.14

IBM AIX 5.1 and 5.2 32/64-bit are no longer supported.

Discontinued As Of: 8.1.000.14

OpenSSL encryption algorithms IDEA, RC4, RC5, and MDC2 are no longer supported.

Discontinued As Of: 8.1.000.14

Oracle 9 is no longer supported.

Discontinued As Of: 8.1.000.14

Red Hat Enterprise Linux (RHEL) AS 3 is no longer supported.

Discontinued As Of: 8.1.000.14

Solaris SPARC 8 is no longer supported.

Discontinued As Of: 8.1.000.14

Top of Page


Internationalization

Information in this section is included for international customers.


When using PostgreSQL with Configuration Server localized for the Japanese market, the localized SQL initialization script can be loaded only if one of the following conditions is met:

The provided initialization script uses UTF-8 encoding.


Top of Page


Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software. Please consult the Framework 8.1 Deployment Guide first.

Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly).

Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.

Top of Page