Configuration Server 8.5.x Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release contains the following new feature or enhancement:
- Support for the Microsoft Hyper-V Server 2016 virtualization platform. Refer to the Supported Operating Environment: Display by Product, Operating System, and Other page for more detailed information and a list of all supported virtualization platforms.
This release contains the following resolved issues:
Configuration Server now correctly stores users' changed passwords when users are forced to change their passwords at login. Previously in this scenario, Configuration Server did not store the new passwords in the Configuration Database, so that every time a user tried to log in again, the new password was rejected and they could log in only using their old password, after which they were prompted to change their password. (MFWK-18928)
Configuration Server no longer writes log file header information continuously to its logs. Previously, this continuous logging caused Configuration Server to use 100% of the CPU. (MFWK-18712)
Configuration Server now prevents an authentication token from being validated and the user authenticated for a time longer than originally intended, in the following scenario:
- The system (server) and client times are synchronized.
- The client generates an authentication token valid for a set time interval; for example, 1:15 to 1:20.
- The system clock is reset to an earlier time; for example, one hour earlier.
- The start time of the token is not affected. In this example, the token is still not valid until 1:15.
Previously in this scenario, the time change affected the start time of the token, so the token was valid from the new server time to the token's original end time. In the example above, the token was valid from 12:15 to 1:20. This enabled the token to be validated and used for a longer time than the client (that created the token) had intended. (MFWK-18656)
If a backup Configuration Server, while switching to primary mode, loses its connection with the database and is forced to reload the data during the switchover, all Virtual Agent Groups now appear properly when the connection is restored. Previously in this scenario, in very rare instances, the VAGs appeared to be empty. (MFWK-18652)
Token-based authentication can now authorize a user if Configuration Server is renamed. Previously in this scenario, the user was not authorized, and received an error message that the database was empty. (MFWK-18628)
In the scenario in which one or more Transport Parameters differ between a primary and backup application, if you change any option in the primary application, the Transport Parameters in the backup application are no longer updated with values in the primary application. Previously in this scenario, the backup application was updated with the value of the Transport Parameter in the primary application. (MFWK-18618)
You can now specify a time interval in which Configuration Server, when connecting to DB Server, will wait for a response from DB Server if a TCP response has not been received because of a network issue. To set the time interval, use the dbserv-conn-async-timeout configuration option in the Configuration Database section of the Configuration Server configuration file. Previously in this scenario, Configuration Server would wait interminably and eventually stop responding. (MFWK-18463)
Configuration Server now passes the correct status of changes in non-Agent Person objects to its interfaces. Previously, it sometimes passed an invalid status, causing the interface to report the Person as Unknown. (MFWK-16996)
No special procedure is required to upgrade to release 184.108.40.206.