Release Note

Contents

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 to all 8.0 releases of Configuration Server.

• Links in the Contents section enable you to access information regarding a specific release. Releases are listed by version number rather than in date order. For this reason, a recent release may be listed after earlier releases, if the version number is lower. Except when otherwise noted in the information for a specific release, each release includes all of the features and corrections that were introduced for the applicable operating system at earlier dates, regardless of the version numbering.
• The Release Number table lists the supported operating systems for each release at a high level. For more detailed information, see the Genesys Supported Operating Environment Reference Manual.
• The Known Issues and Recommendations section is a cumulative list. It includes information on when individual items were found and, if applicable, corrected.
• The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
• The Discontinued Support section is cumulative. It lists functionality that is no longer supported and the release number of the version in which support was discontinued.

Use of Third-Party Software

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

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# 304906112)

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

Writeable 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# 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# 301075007)

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# 300359195 [299888531, 298358682, 297879796])

Top of Page

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:

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# 296487805)

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# 297879383 [296915383])

You can now update Voice Platform Profile objects using Configuration Server Proxy. (ER# 293531016)

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

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# 297317975 [284247665])

If password validation rules (introduced in Configuration Server 8.0.300.49) are enabled for a Tenant, newly created Person objects created under that Tenant 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, but could be found using search functionality. (ER# 295432928)

When using LDAP external authentication, Configuration Server no longer runs out of memory under normal circumstances. Previously, responses from the LDAP Server were not being released to Configuration Server, and the expanding queue of unreleased messages used memory. (ER# 298936760)

Top of Page

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 no longer stops authenticating users using LDAP external authentication if a request containing an error is rejected by the LDAP server. Now, Configuration Server skips this request and continues to send authentication requests as usual. Previously, Configuration Server would stop responding, waiting for the problematic request to be authenticated. Normal processing would resume only after Configuration Server was restarted. (ER# 287507463)

This version of Configuration Server includes an updated library for LDAP external authentication. Previously, the LDAP authentication process sometimes stopped working and required a restart of Configuration Server to get the LDAP external authentication functionality working again; in some cases, Configuration Server terminated unexpectedly. (ER# 259528441)

Top of Page

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 no longer terminates in the following scenario:

1. An Application or a Person object is deleted.
2. An application connected to Configuration Server on behalf of the deleted object continues to run after the deletion.

Previously in this scenario, Configuration Server in most cases would not terminate immediately after the deletion. The termination would occur after some delay, sometimes significant, and when Configuration Server attempted to process a request from, or send a notification to, the application.

(ER# 289231965)

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# 287910653)

Configuration Server no longer stops authenticating users using LDAP external authentication if a request containing an error is rejected by the LDAP server. Now, Configuration Server skips this request and continues to send authentication requests as usual. Previously, Configuration Server would stop responding, waiting for the problematic request to be authenticated. Normal processing would resume only after Configuration Server was restarted. (ER# 287507463)

Note: This correction does not work in some scenarios. The issue was reopened, and a complete fix is available in release 8.0.300.54.

Top of Page

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:

When running on the Linux platform, Configuration Server Proxy no longer produces a core file when the connection to the master Configuration Server is lost while retrieving data from the master Configuration Server was lost. (ER# 288453370)

Configuration Server Proxy no longer risks the possibility of storing duplicate configuration data and passing it on to its clients, as described in the following scenario:

1. Upon startup, Configuration Server Proxy sends a series of requests to the master Configuration Server to retrieve configuration data.
2. After this data retrieval is complete, Configuration Server Proxy allows its clients' connections, and forwards some requests to the master Configuration Server on their behalf.
3. If the seventh request (in the sequence of forwarded client requests) triggers an error message, for any reason, from the master Configuration Server, Configuration Server Proxy mistakenly interprets the error as having occurred at the beginning of the data retrieval mentioned in step 1 of this scenario.
4. Configuration Server Proxy then starts data retrieval from the master Configuration Server all over again, without deleting its current data. As a result, Configuration Server Proxy may store duplicate configuration data in its cache, and in turn send duplicated configuration data to its clients.

Now, Configuration Server handles the error message after the seventh request properly, and does not restart data retrieval.

(ER# 288005882)

Top of Page

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 contains the following new features or functionality.

• Configuration Server has been enhanced to support the following security-related features: password rules by validating specific characters in a password, and authentication rules by locking user accounts based on a configured number of unsuccessful login attempts during a specified time interval.

• Using the following configuration options, you can configure password rules for a particular Tenant that will be applied to any user account under this Tenant. These options must be set in the security-authentication-rules section of the Tenant object (Annex tab).

  password-req-number
  Default Values: false
  Valid Values: true, false
  Changes Take Effect: At the next password change

  Specifies whether Configuration Server validates the presence of at least one numeric character in a password. If this option is set to true and there are no numeric characters in the password, Configuration Server will reject the password with the following error message: Password rejected: At least one numeric character is required.
  Note: This password rule does not apply to empty passwords if they are configured.

  password-req-mixed-case
  Default Values: false
  Valid Values: true, false
  Changes Take Effect: At the next password change

  Specifies whether Configuration Server validates the presence of US-ASCII alphabetic characters in both upper and lower case in a password. If this option is set to true and there are no alphabetic characters in both cases in the password, Configuration Server will reject the password with the following error message: Password rejected: At least one upper and one lower case ASCII character is required.
  Note: This password rule does not apply to passwords that contain only numeric characters, or to empty passwords if they are configured.

  password-req-alpha
  Default Values: false
  Valid Values: true, false
  Changes Take Effect: At the next password change

  Specifies whether Configuration Server validates the presence of at least one US-ASCII alphabetic character in a password. If this option is set to true and there are no alphabetic characters in the password, Configuration Server will reject the password with the following error message: Password rejected: At least one US-ASCII alphabetic character is required.
  Note: This password rule does not apply to empty passwords if they are configured.

• Configuration Server can now track the number of unsuccessful login attempts during a specified period of time after a first unsuccessful login attempt. When the number of unsuccessful attempts is reached for a specific user account on a specific Configuration Server, that Configuration Server stops authorizing authentication requests for that user account and responds with an error message. Configuration Server keeps the account locked for a configured period of time until the time interval expires. Note that Configuration Server does not count unsuccessful login attempts and does not lock accounts that have been disabled or have been configured to override the lockout setting.

  Tenant-Level Options

  These options must be set in the security-authentication-rules section of the Tenant object (Annex tab):

  account-lockout-threshold
  Default Values: 0 (the account is not locked)
  Valid Values: An integer from 0 to 8 (retries)
  Changes Take Effect: At the next unsuccessful login attempt
  

  Specifies whether Configuration Server locks an account after the maximum number of unsuccessful attempts is reached. In other words, when this option is set to a value of other than 0 (zero), it specifies the number of unsuccessful login attempts that a user can make before the user account is locked. If this option is set to 0 (the default), the account is not locked.
  Note: A user must set this option to activate the account lockout feature (for relevant Tenants).

  account-lockout-duration
  Default Values: 30 (minutes)
  Valid Values: An integer from 0 to 1440
  Changes Take Effect: Immediately

  Specifies the period of time, in minutes, for an account to remain locked. After this timeout expires, the account in question is released. This option applies only if the account-lockout-threshold option is set to a non-zero value.

  account-lockout-attempts-period
  Default Values: 0
  Valid Values: An integer from 0 to 20
  Changes Take Effect: Immediately

  Specifies the period of time, in minutes, the account lockout threshold is maintained. If a user logs in to the account successfully, the threshold is reset. If this period of time expires, the threshold is also reset. If the option is set to 0 (the default) or is empty, it disables the feature, because any subsequent attempt will never get into the specified period. This option applies only if the account-lockout-threshold option is set to a non-zero value.

  Person-Level Option

  To override Tenant's account lockout options for a particular Person/account, use the account-override-lockout option that must be set in the security-authentication-rules section of the Person object (Annex tab):

  account-override-lockout
  Default Values: false
  Valid Values: true, false
  Changes Take Effect: At the next login attempt

  Specifies whether Configuration Server counts unsuccessful login attempts of a particular Person to determine if the Person's account will be locked. If this option is set to true, it overrides the account lockout options set at the Tenant level, and the account will not be locked. If this option is set to false (the default), the account lockout options set at the Tenant level will apply.
  Note: An administrator can unlock a Person's account before the lockout duration expires by changing the Person�s account-override-lockout option to a value of true.

  (ER# 280547792)

Corrections and Modifications

This release does not include any corrections or modifications.

Top of Page

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 uses a new algorithm when it prepares messages to be sent to client applications. Previously, when responding to a client application request, Configuration Server could report a message packing error when attempting to pack large objects configured in the Configuration Layer. (ER# 283975913)

A Configuration Server client that is running a 7.6 release now starts properly if there is one or more key-value pairs configured in the Annex tab of the client object with a value that is exactly 255 characters. Previously in this scenario, Configuration Server would not allow the client to start properly. (ER# 283181468)

Previously, when configured to use both LDAP external authentication and open secure (TLS) ports, Configuration Server terminated unexpectedly at startup on UNIX platforms. To prevent this problem from occurring on Linux and HP-UX platforms, upgrade Configuration Server to this release, and upgrade Genesys Security Pack on UNIX to release 8.0.300.00 or 8.1.000.01. (ER# 284577052)

Top of Page

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:

If Configuration Server has successfully established a connection to an LDAP Server but for some reason continues to retry an external authentication request, it now limits the number of retries to that specified by the option retry-attempts. Previously, Configuration Server did not use this option in this situation and retried the request indefinitely, consuming Configuration Server and LDAP Server resources and creating significant delays in the processing of other authentication requests. (ER# 279960061, 279159929)

Top of Page

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 correctly identifies itself and its version number in the HTTP headers of SOAP messages, as follows: Server:Genesys-Config/8.x.xxx.xx. Previously in these headers, Configuration Server incorrectly identified itself to SOAP clients as a Microsoft-IIS/4 server. (ER# 257545289)

Top of Page

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 section describes new features that were introduced in this release of Configuration Server.

• The new writable Configuration Server Proxy enables direct creation, modification, and deletion of configuration objects, including access permissions for those objects, by any of its clients. Use the existing configuration option proxy-writable in the csproxy section of the Configuration Server Proxy Application object to enable or disable this functionality.

  To implement this, the functionality of the option proxy-writable has been extended to enable all client applications of the Configuration Server Proxy, not just Genesys Agent Desktop applications, to request changes. Refer to the Framework 8.x Configuration Options Reference Manual for full details about this option.

  (ER# 264422916)

Corrections and Modifications

This release includes the following corrections and modifications:

Configuration Server Proxy now properly handles SOAP requests to delete objects. Previously, Configuration Server Proxy would terminate unexpectedly when it received a SOAP request for a deletion, resulting in a transaction rollback. (ER# 266412174, 283904309)

Configuration Server Proxy now generates the correct notification for a new object that is created in a location other than the default location (for example, if a new Place object is created in a subfolder of Configuration/<Tenant name>/Resources/Places). Previously, Configuration Server Proxy would incorrectly include the DBID of the default location, not of the actual location, in its notification. (ER# 264384311)

After Configuration Server Proxy restarts, it now correctly creates a connection to Message Server. Previously in this scenario, Configuration Server Proxy was sometimes unable to establish the connection. (ER# 262096571)

History of Changes Adapter (HCA) functionality is now working properly. Previously, after migrating from 7.6 to 8.0.3, HCA functionality did not work. (ER# 256081408)

Top of Page

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, HP-UX, Solaris, and Windows platforms, Configuration Server 8.0.300.30 was tested on the Linux and Tru64 UNIX platforms. On October 25, 2010, the release type for all platforms changed from Hot Fix to General.

Corrections and Modifications

This release includes the following corrections and modifications:

Configuration Server startup performance is now improved when the history records contain large deltas. Previously, large deltas in the history records increased the time it took for Configuration Server to start. (ER# 261157107)

This release eliminates the memory leak that occurred in the following scenario:

• Person configuration objects (agents and non-agents) are being created or updated.
• The backup Configuration Server and/or Configuration Server Proxy are running and connected to the primary Configuration Server.

Previously, Configuration Server experienced memory growth at a rate proportional to the rate of Person updates multiplied by the number of Configuration Server Proxies used.

(ER# 260503661)

Configuration Server Proxy in writable mode now updates its History Log correctly, thereby enabling a successful restoration of the client session if required. Previously, Configuration Server Proxy sometimes generated records with duplicate IDs that could not be written to the History Log, and therefore any restoration of a client session was incorrect.

Note: Both the master Configuration Server and Configuration Server Proxy must be updated to fix this problem.

(ER# 256659979)

A client of Configuration Server is now unable to restore a session with Configuration Server but has to reread the configuration if, while the client was not connected, one or more changes were made in the permissions of any objects to which the client was subscribed. Previously in this scenario, the client was able to restore the session to Configuration Server successfully, but did not receive all history notifications about these changes. (ER# 255472609)

After a series of switchovers, the Configuration Server that is running in Primary mode now has a complete view of the Configuration Database and recognizes incoming clients. Previously, the Configuration Server running in primary mode sometimes lost track of the Configuration Database and was unable to authenticate clients. (ER# 252107271, 234840756)

Top of Page

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 section describes new features that were introduced in this release of Configuration Server.

• To ensure that Configuration Server functions properly when saving a client session to the History Log after the client (which had a large number of subscriptions) disconnects, a limit of 40,000 subscriptions per client per session is introduced. A session in which a client has more than that limit will not be recorded in the History Log, and a corresponding message will be logged by Configuration Server. (ER# 256680781)

• Advanced Disconnect Detection Protocol (ADDP) is now supported between primary and backup Configuration Servers. Use the new configuration options protocol, addp-timeout, addp-remote-timeout, and addp-trace, setting them in the configuration server section of the configuration files for both Configuration Servers. For the primary Configuration Server, this section is called confserv. For the backup Configuration Server, this section has the same name as the backup Configuration Server Application object.

  protocol
  Default Value: No default value
  Valid Values: addp
  Changes Take Effect: After restart
  
  Specifies if ADDP is to be used between the primary and backup Configuration Servers. If set to addp, the ADDP protocol is implemented as defined by the ADDP-related configuration options addp-timeout, addp-remote-timeout, and addp-trace in the same configuration server section (confserv, or its equivalent in the backup Configuration Server) of the configuration file. If this option is set to any other value, or if it is not specified at all, ADDP is not used and the ADDP-related configuration options in this section are ignored.

  Note:The three options below have the same names as other options that already exist in Genesys software. While all are used to implement ADDP, the placement of each option (in configuration section and, in some cases, configuration object) is unique and determines the use thereof. The options described below do not replace these pre-existing options.

  addp-timeout
  Default Value: 0
  Valid Values: 0–3600
  Changes Take Effect: After restart
  
  Specifies the time interval, in seconds, that Configuration Server in backup mode waits before polling the other Configuration Server in the redundant pair. If set to zero (0), Configuration Server in backup mode does not poll the other Configuration Server in the redundant pair. This option applies only if the value of the protocol option is addp.

  Note: Because any Configuration Server can be in primary or backup mode, regardless of how it is configured, you must set this option to the same value in both the primary and backup Configuration Servers.

  addp-remote-timeout
  Default Value: 0
  Valid Values: Any positive integer
  Changes Take Effect: After restart
  
  Specifies the time interval, in seconds, that Configuration Server in backup mode instructs the other Configuration Server in the redundant pair to use when polling to check the connection between the two servers. If set to zero (0), Configuration Server in backup mode does not send any such instruction. This option applies only if the value of the protocol option is addp.

  Note: Because any Configuration Server can be in primary or backup mode, regardless of how it is configured, you must set this option to the same value in both the primary and backup Configuration Servers.

  addp-trace
  Default Value: off
  Valid Values:
  

  	false, no,off	No ADDP trace occurs
  	true, yes, on, local	ADDP trace occurs on the side of the Configuration Server in backup mode.
  	remote	ADDP trace occurs on the side of the Configuration Server in primary mode.
  	both, full	ADDP trace occurs at both the primary and backup Configuration Servers.

  Changes Take Effect: After restart
  
  Determines whether ADDP messages are written to the primary and backup Configuration Servers log files. This option applies only if the value of the protocol option is addp.

  Example: In the Configuration Server configuration file, the ADDP options would appear as follows:
  
  [confserv]

...

protocol=addp

addp-timeout=16

addp-remote-timeout=32

addp-trace=both

...

  For more information about ADDP, refer to the Framework 8.0 Deployment Guide.

  Note: ADDP is disabled while the backup Configuration Server is initially reading configuration data, or rereading it after reconnection, from the primary Configuration Server.

  (ER# 254468865)

Corrections and Modifications

This release also includes the following corrections and modifications:

This release eliminates the memory leak that occurred in the following scenarios:

• Configuration Server received XML requests (other than AddObject) from clients through the SOAP port. (ER# 259510443)
• Configuration Server had to withhold some History Log records from a client that had requested all records, but whose configured permissions did not allow it access to all of the records. (ER# 254217691)
• Configuration Server received a client subscription request that was already registered, and did not check if it was a duplicate. (ER# 254154971)

Previously, these memory leaks sometimes caused Configuration Server to terminate because of lack of memory.

Configuration Server Proxy now reads all configuration data correctly when it is using a schema version different than the master Configuration Server. To enable this, you must set the new configuration option fix_cs_version_7x to true in the master Configuration Server's configuration file confserv.cfg (Windows) or confserv.conf (UNIX). Previously, without this new option, Configuration Server Proxy would use an incorrect schema, and then read the data incompletely or incorrectly.

[confserv]
fix_cs_version_7x
Default Value: false
Valid Values: true, false
Changes Take Effect: After restart

Use this option when using a master Configuration Server running release 8.0.3 with a Configuration Server Proxy running a pre-8.0 version. Setting this option to true enables the master Configuration Server to treat Configuration Server Proxy as running an equivalent schema. This prevents Configuration Server Proxy from using an incorrect schema and reading configuration data incorrectly.

Note: Use this option only when migrating Configuration Server from a pre-8.0 version to the 8.0.3 version. This option does not apply to any other scenario.

(ER# 256484431)

Configuration Server now initializes correctly at restart. Previously, it initialized Virtual Agent Groups (VAGs) twice, generating the appropriate error messages, and started without being correctly initialized. (ER# 256025208)

Clients can again connect to the autodetect port of Configuration Server. Previously, after Configuration Server was upgraded to release 8.0.3, the autodetect port was unavailable. (ER# 255990856)

The backup Configuration Server now successfully switches to primary mode without rereading configuration data if it was disconnected from the primary Configuration Server at the same time as some clients were disconnecting from the primary Configuration Server. Previously in this scenario, the backup Configuration Server would delay switching to primary mode until it had reread the configuration data. (ER# 255250934)

Existing Virtual Agent Groups are now updated properly after a Skill object is deleted. (ER# 255110541)

Switchover of a backup Configuration Server Proxy to primary mode no longer occurs with incomplete data; switchover occurs only after the backup Configuration Server Proxy has completed reading all configuration data. In other words, the ports of the backup Configuration Server Proxy open only after all configuration data has been read.

Previously, even if the backup Configuration Server Proxy was in the process of reading configuration data, switchover would occur immediately. That is, Configuration Server opened its ports before all the configuration data was read. As a result, clients that subsequently reconnected to that Configuration Server Proxy had access to incomplete out-of-date data.

(ER# 254741973)

Configuration Server now loads 3-level annexes correctly, so that identical options (on the third level) in different sections (on the second level) can be read correctly. In previous releases, the data was read incorrectly, and clients using 3-level annexes sometimes received incorrect warnings when processing their data. (ER# 254381912)

Users whose passwords have been changed using the master Configuration Server after upgrading to 8.0.2 can now connect to an associated Configuration Server Proxy. This problem was specific to the HP-UX 64-bit platform. (ER# 254344366)

When using LDAP external authentication, Configuration Server no longer rejects authentication requests when an internal LDAP error occurs or if there is a communication link failure between Configuration Server and the LDAP Server. Previously in this scenario, Configuration Server would display an error message indicating that the user password was incorrect, but would not allow any user authenticated by LDAP to log in, regardless of password. The only way to fix the problem was to restart Configuration Server. (ER# 254162157)

ADDP now works properly between the master Configuration Server and Configuration Server Proxies with which it is associated. Previously, the master Configuration Server started sending ADDP polling to Configuration Server Proxy while it was initializing. This sometimes caused Configuration Server Proxy to disconnect from the master Configuration Server because of the expiration of the ADDP timeout (specified by the configuration option addp-timeout). (ER# 254155311)

If unexpected internal errors are detected, Configuration Server now generates log event 00-09999 for further diagnosis. Previously, Configuration Server did not generate the log event, and would terminate instead.

Note: 00-09999 can be used as an alarm generation event for the detection and diagnosis of internal Configuration Server errors.

(ER# 253329622, 226575276)

Configuration Server no longer terminates unexpectedly when it finishes processing a large XML update that contains multiple add and delete commands for one object, and that is received from a client using the SOAP port. (ER# 250722183)

Previously, Configuration Server Proxy sometimes terminated when its clients disconnected after it had lost its connection with the master Configuration Server. This issue has been fixed. (ER# 244020354)

The backup Configuration Server no longer terminates if, after being instructed to switch to Primary mode, it is instructed to switch to Backup mode before it has completed processing the earlier request. The proximity of the two requests may be the result of a network outage on the host where the original primary Configuration Server is running.

Previously, the backup Configuration Server terminated if it received two opposing requests (switch to primary and switch to backup) consecutively and within a short period of time.

(ER# 242922873, 223607407, 223382342, 135171302)

In a redundant configuration, the primary and backup Configuration Servers can start simultaneously. Previously, one or both of the two servers in the redundant pair sometimes stopped executing. (ER# 236730387, 232761114, 227204269, 219446302)

After losing its connection with the main Configuration Server while reading configuration data, Configuration Server Proxy now reconnects automatically to the main Configuration Server and continues executing. Previously, Configuration Server Proxy would sometimes just terminate. (ER# 236050710)

Configuration Server no longer terminates when an unexpected request is received through the SOAP port. (ER# 226894211)

Configuration Server no longer produces a core file during shut down. Previously, Configuration Server sometimes produced a core file while closing communication channels with client applications for which unprocessed data still existed in the incoming queue. (ER# 225226451)

Configuration Server now logs which ports it cannot open. (ER# 106201080)

Top of Page

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.

• Configuration Server can now be configured to require that passwords used by all users configured in a Tenant be of a minimum length.

• Configuration Server now supports the use of commas (,) as delimiters in HTTP strings used in cookies in SOAP requests. (ER# 229931695)

• Configuration Server now supports the Red Hat Enterprise Linux (RHEL) 5.4 operating system.

• Configuration Server now supports a PostgreSQL Configuration Database.

Corrections and Modifications

This release also includes the following corrections and modifications:

Configuration Server now recalculates Virtual Agent Groups in the following scenario:

1. Configuration Server loses its connection with DB Server and runs in Read-Only mode.
2. Configuration Server restores the connection with DB Server, and rereads configuration data.

Previously in this scenario, Virtual Agent Groups were not initialized and remained empty.

(ER# 253091582)

Configuration Server now correctly sends to the client all Campaign Group data. Previously, the value in the Voice Transfer DN field was lost during data transfer. (ER# 252470958)

Configuration Server now correctly sends error messages to the appropriate clients. Previously, it sometimes sent error messages relating to previous requests to clients for which requests were being processed. (ER# 246969072)

The text of log events 00-04503 and 00-04504 now include the attribute [server name] as specified in Framework Combined Log Events Help. (ER# 223692755)

Top of Page

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 operates properly after sending a series of authentication requests to the LDAP external authentication module. Previously, Configuration Server sometimes terminated on UNIX platforms. On Windows platforms, the LDAP module sometimes terminated unexpectedly and Configuration Server continued running with no active LDAP authentication. (ER# 247452757)

Top of Page

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.

• The new configuration option allow-external-empty-password enables you to control whether you will allow empty passwords to be accepted for external authentication.

  allow-external-empty-password
  Default Value: true
  Valid Values: true, false
  Changes Take Effect: After restart

  When this option is set to true (the default), the existing behavior of Configuration Server is preserved, and the processing of external authentication requests with empty (blank) passwords depends on the value of the option allow-empty-password. When this option is set to false, Configuration Server rejects all external authentication requests with a blank password.

  Refer to the Framework 8.0 Configuration Options Reference Manual for more information about these two options and how they work together.

• Configuration Server now supports the Last Login feature implemented in many Genesys Graphical User Interfaces, such as Configuration Manager and Solution Control Interface. Two new options, last-login and last-login-synchronization, help you to manage this feature. For more information about this feature and these new options, refer to the latest version of the Genesys Security Deployment Guide.

• By default, members of the EVERYONE access group have no access to configuration objects during database initialization.

Corrections and Modifications

This release also includes the following corrections and modifications:

When the configuration option allow-empty-password is set to false, Configuration Server no longer allows you to create a Person/User with an empty (blank) password, or to change a password to such a value. Previously, a user could have an empty password, but could not log in with it. (ER# 170899385)

Configuration Server now accepts non-ASCII characters in LDAP authentication requests. (ER# 221506513)

Overriding the default LDAP search filter at the Person level (in the field External User ID) now works properly. (ER# 230620003)

Configuration Server no longer permits the deletion of an Agent Group if it is linked to a Campaign Group. (ER# 233398345)

If both LDAP and RADIUS external authentication modules are specified by the library option, and the file ldapclient.conf already exists in the installation directory, you can use both LDAP and RADIUS as configured. Previously in this case, the RADIUS module was not loaded during Configuration Server startup. (ER# 235046513)

In the following scenario, Configuration Server Proxy now uses RADIUS external authentication as configured:

1. LDAP external authentication is configured on the master Configuration Server.
2. RADIUS external authentication is configured on Configuration Server Proxy.
3. Configuration Server Proxy tries to authorize a client with an empty External User ID field.

Previously, Configuration Server Proxy would perform only internal authorization.

(ER# 235405581)

Configuration Server now responds correctly to authentication requests when LDAP external authentication is used and the LDAP API functions return negative error codes. (ER# 235821515)

Configuration Server now displays the correct version of the external LDAP library in logs. (ER# 236245933)

Top of Page

Supported Operating Systems

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

New in This Release

This release is under shipping control. This section describes new features that were introduced in this release of Configuration Server.

• Configuration Server now supports Hierarchical Multi-Tenant configurations, where each Tenant object is a parent, child, or both.

• Configuration Server supports Emergency Mode, which allows only members of the Super Administrators access group to make changes to the Configuration Database.

• Network traffic is optimized for connections between Configuration Server and its clients.

• Configuration Server now supports Oracle LDAP Proxy/Internet Directory external authorization.

• When a user attempts to log in to Configuration Server, and external authentication is being used, Configuration Server now relays messages from the RADIUS or LDAP server to the user.

• New log events 21-24100, 21-24101, and 21-24102 enable users to better monitor the connection between Configuration Server and the RADIUS or LDAP server.

• Users who have been disabled in Genesys Administrator or Configuration Manager cannot log in to Genesys applications. In a single-tenant environment, all users cannot be disabled in a single action (by disabling the Environment tenant).

• The following additional types of configuration objects are now supported:

  • Application types—Advisors, Customer View, ESS Extensible Services, Interaction Workspace, and SMS Server
  • Script types—ESS Dial Plan, Interaction Workflow Trigger, and Outbound Schedule
  • Switch types—Avaya TSAPI and Huawei NGN

  In addition, the Contact Type type Instant Messaging is now supported for the Outbound Contact Solution.

• This version of Configuration Server Proxy requires 8.0 versions of the technical licenses.

Corrections and Modifications

This release also includes the following corrections and modifications:

Configuration Server no longer permits a user with an empty password to insert any string of characters as their old password when changing their password. Such requests are rejected, and an error message generated. (ER# 222069795)

Configuration Server now accepts and stores blank (empty) configuration option values. Previously, such values could not be stored in the Configuration Database. (ER# 216459073, 217700045)

Top of Page

Supported Operating Systems

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

New in This Release

This release is under shipping control. This section describes new features that were introduced in the initial 8.0 release of Configuration Server.

• Configuration Server now supports the Genesys Voice Platform (GVP) Solution, and new GVP-specific objects have been introduced. These GVP-specific objects are stored in the Configuration Database, and are configured and maintained using the new Genesys Administrator, or using Configuration Manager and Solution Control Interface. Refer to the Framework 8.0 Deployment Guide and to GVP-specific documentation for more information.
  
  
• Configuration Server now includes metadata, which provides you with a more user-friendly way to configure Configuration Server. The metadata contains all runtime configuration options supported by Configuration Server in Master mode and Configuration Server in Proxy mode. This metadata is supported only by the new web-based Genesys Administrator. For more information about metadata, refer to Framework 8.0 Genesys Administrator Help.

Corrections and Modifications

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

In debug logs, Agents skill levels changed to 0 (zero) are displayed as level deleted. Previously, the value of the skill level before the change was displayed. (ER# 144342854)

Obsolete application type SIP Communication Server is no longer supported by Configuration Server, and does not appear as an option in any list. (ER# 150229301)

Configuration Server now uses the specified retry-attempts and retry-interval values specified for LDAP external authentication. Previously, Configuration Server ignored the specified values and used the default values instead. (ER# 150236199)

Configuration Server no longer terminates when working with external authentication. Previously, under a heavy load, Configuration Server sometimes terminated abnormally when trying to externally authenticate a user. (ER# 176892421)

Configuration Server initialization now completes successfully in those cases where Advanced Disconnect Detection Protocol (ADDP) is activated between Configuration Server and Configuration DB Server. Previously, when the ADDP timeout was short enough and the Configuration Database large enough, sometimes the ADDP timeout expired and prevented the proper initialization of Configuration Server. (ER# 182717445)

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.

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)

When using LDAP external authentication, if the option allow-empty-password is set to true, Configuration Server passes authentication requests with empty (blank) passwords to the LDAP server, ignoring the value of the option allow-external-empty-password. (ER# 296487805)

If Configuration Server Proxy loses its connection to the master Configuration Server while retrieving data, Configuration Server Proxy does not load data and shuts down.

Workaround: To mitigate this problem, configure the start of Configuration Server Proxy as an Alarm Reaction to the Alarm Condition Application failure of Configuration Server Proxy.

(ER# 288709821)

Configuration Server using LDAP external authentication stops authenticating users if a request containing an error is rejected by the LDAP server.

Workaround: When this occurs, restart Configuration Server. User authentication will then continue as usual. (ER# 287507463)

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)

If a Tenant is disabled by using Configuration Server Proxy, Configuration Manager connected to that Configuration Server Proxy shows only the top-level folder as disabled; all folders and files contained in that top-level folder are still active. However, Configuration Manager connected to the main Configuration Server or any other Configuration Server Proxy properly shows all folders and files of the disabled Tenant as disabled. (ER# 271201450)

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. (ER# 269933185)

When a new object is created in Configuration Server Proxy, and the main Configuration Server switches over, a duplicate object is created in the database. (ER# 268804508)

Existing Virtual Agent Groups are not updated if a skill object is deleted. (ER# 255110541)

Last Login information is not synchronized between the main Configuration Server and Configuration Server Proxies. For example, if a user logs in to the main Configuration Server, then logs in to a Configuration Server Proxy, the Last Login information displayed the second time does not reflect the login attempt to the main 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 (main or Proxy).

(ER# 241981648 )

Consider the scenario in which LDAP external authentication is configured on the master Configuration Server and RADIUS external authentication is configured on Configuration Server Proxy. If, in this case, Configuration Server Proxy tries to authorize a client with an empty External User ID field, Configuration Server Proxy performs internal authorization. (ER# 235405581)

If both LDAP and RADIUS external authentication are configured, you cannot use the file ldapclient.conf. You can only specify one LDAP server in the Configuration Server configuration file (confserv.cfg or confserv.conf). (ER# 235046513)

Configuration Server erroneously permits the deletion of an Agent Group even if it is linked to a Campaign Group. (ER# 233398345)

Overriding the default LDAP search filter at the Person level (in the field External User ID) does not work properly. (ER# 230620003)

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

The Framework 8.0 External Authentication Reference Manual contains incorrect descriptions of the configuration option library and the section in which it is contained, authentication. The correct descriptions are:

[authentication]
This section indicates that RADIUS external identification is to be used.

library
Specifies gauth_radius as the section that specifies the output level for debugging information produced by the Authentication Module. This option is mandatory, and its value is set automatically during installation.

Example: The following is an example of the authentication section in a Configuration Server configuration file:

   [authentication]
   library=gauth_radius

(ER# 215640647)

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.0 Deployment Guide instead. (ER# 193827147)

Configuration Server does not accept non-ASCII characters in LDAP authentication requests. (ER# 221506513)

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)

Configuration Server does not log which ports it cannot open. (ER# 106201080)

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.

HP-UX 11.00 is no longer supported.

Solaris 7 is no longer supported.

Windows 2000 is no longer supported.

Top of Page

Internationalization

Information in this section is included for international customers.

There are no limitations or restrictions for internationalization.

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.0 Deployment Guide first.

• Framework 8.0 Deployment Guide provides instructions for installing and configuring Framework 8.0 components, and for starting and stopping Framework 8.0 components either using the Management Layer or manually.

• Framework 8.0 Genesys Administrator Deployment Guide provides instructions for installing, configuring, logging in to, and logging out of Genesys Administrator. Some troubleshooting information related to the setup of Genesys Administrator is also included.

• Framework 8.0 Configuration Options Reference Manual describes configuration options for Framework 8.0 components.

• Framework 8.0 Configuration Manager Help describes how to use Configuration Manager in either an enterprise or multi-tenant environment.

• Framework 8.0 Genesys Administrator Help describes how to use Genesys Administrator in either an enterprise or multi-tenant environment.

• Framework 8.0 Combined Log Events Help describes log events that Genesys server applications generate and that Genesys Administrator and Solution Control Interface display.

• Framework 8.0 External Authentication Reference Manual describes how to use RADIUS and LDAP external authentication systems with Configuration Server.

• Genesys 8.0 Security Deployment Guide describes Genesys security features and detailed instructions for deploying them. These features provide secure data transfer between Genesys components, protection against unauthorized access, and protection against data loss in case of component failure.

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

Note: For the DVD/CD, the New Documents on this DVD/CD 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