Recording Crypto Server Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
|06/29/16||General||Under Shipping Control||X||X|
This release includes only resolved issues.
This release contains the following resolved issues:
The Recording Crypto Server (RCS) now terminates when keystore read fails after a configured number of attempts on start-up. The behavior is controlled by the following configuration options:
max-read-attempts: Specifies maximum number of attempts to read keystore on start-up.
Default Value: 5
Valid Values: -1, or positive integer
If -1 is specified as value RCS will retry endlessly.
read-interval: Specifies time interval in seconds between keystore read attempts.
Default Value: 1
Valid Values: 1-30
When debug logging is enabled, the RCS no longer exposes the Base64-encoded Authorization header in the log file when sending requests to Genesys Web Services, when debug logging is enabled. (GIR-4401)
The RCS no longer throws an exception if the keystorepassword is empty. Previously, it threw an exception and decryption would fail in this scenario. (GIR-5725)
No special procedure is required to upgrade to release 8.5.050.73.