Release Notes V10.1.0 Fix Pack 2

A summary of changed or new features and enhancements included in Remote Control Fix Pack 2.

Remote Control V10.1.0 Fix Pack 2 GA

Features that are introduced in Remote Control V10.1.0 Fix Pack 2
  • Microsoft Entra ID Support

    In this release, Remote Control introduces Microsoft Entra ID support. It is now possible to use Microsoft Entra ID to enable the authentication of the users and their associated group membership into the Remote Control Server. A new synchronization task is available in order to synchronize all the users and the groups changes in Microsoft Entra with the Remote Control database.

    For more information, refer to our product documentation.

  • Login Disclaimer

    With Fix Pack 2, you can now configure a custom disclaimer in order to display a title and a content after the login of every user into the Remote Control server. This new feature is useful in displaying a notice before reaching the homepage.

  • MacOS Sequoia (version 15) Support

    With Fix Pack 2, Remote Control Target now supports macOS Sequoia (version 15).

  • Linux Target are now supported with native 64-bit version packages

    With Fix Pack 2, Linux Remote Control targets are now available for 64-bit architecture. They no longer require installing 32-bit compatibility libraries.

  • Clipboard transfer from the Controller to the macOS Target and vice-versa

    With Fix Pack 2, it is now possible to transfer clipboard data from the Remote Control Controller to the macOS Target and vice-versa.

  • IBM FIPS Provider 140-3 with TLSv1.3 Support

    With Fix Pack 2, Remote Control Server is using the IBM Java JCE FIPS 140-3 Cryptographic Module (IBMJCEPlusFIPS). The FIPS 140-3 cryptographic security standard from the US government supersedes the previous version, FIPS 140-2 standard. With the adoption of the IBM Java JCE FIPS 140-3 Cryptographic Module the Remote Control Server now supports FIPS with TLS 1.3.

    The usage of NIST SP 800-131A has been deprecated.

  • Hostname Verification

    With Fix Pack 2, Remote Control Server now performs hostname verification on SSL certificates. This means that the runtime checks to make sure that the hostname or IP address from the component certificate's Subject Alternative Name (SAN) matches the hostname or IP address used when establishing the connection. New configuration properties are available to accommodate certificates that do not pass this verification step. For more information, refer to Hostname verification for Liberty.

  • Serviceability Enhancements

    With Fix Pack 2, a new warning message is added into the Remote Control server log file if Derby is used as DBMS in order to make the Administrator aware that it is only recommended for Proof of Concept deployments.