Configuration Server 8.5.x Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release contains the following new features and enhancements:
- Clusters of Configuration Server Proxies can now support load balancing using the F5 load-balancer for agent-facing applications.
- 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. Configuration Server ignores all other attributes.
- A new component, Configuration Database Maintenance Scripts, enables upgrade of the Configuration Database schema and locale without upgrading the Configuration Layer as a whole, and with minimal disruption to operations.
- Instructions for upgrading Management Framework components to release 8.5 and later have been completely rewritten in a more concise and clearer manner. Refer to the Framework Migration Guide.
This release contains the following resolved issues:
Configuration Server now uses internal authentication for a user configured with library=internal and with a non-empty External User ID field. Previously, Configuration Server placed less priority on the library option and read only the External User ID field, thereby using external authentication for that user. (MFWK-16779)
Configuration Server now disables external authentication at the Person level if the library option in the [authentication] section is set to internal. Previously in this scenario, Configuration Server did not disable external authentication. (MFWK-16761)
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-16484)
No special procedure is required to upgrade to release 220.127.116.11.