Known issues in OpenEdge 12.2.18

Beginning with OpenEdge version 12.2.18, Remote RMI is disabled by default as part of a security enhancement. This change affects remote calls made by utilities related to the following components:

• NameServer
• DataServer for Microsoft SQL Server
• DataServer for Oracle
• dbman

If your environment relies on Remote RMI functionality, you can re-enable it by updating the $DLC/properties/AdminServerPlugins.properties configuration as follows:

1. In both the AdminServer and ProAdsv sections, add the enableRemoteRMI property to true within jvmargs.

   For example:

   
   												[PluginPolicy.Progress.AdminServer]
   												pluginclasspath=!{value-of:classpath}
   												classpath=...
   												jvmargs=-DenableRemoteRMI=true
   												
   												[PluginPolicy.Progress.ProAdsv]
   												pluginclasspath=!{value-of:classpath}
   												classpath=...
   												jvmargs=-DenableRemoteRMI=true
   											

The default HTTPS configuration for .NET Open Client has changed to use TLSv1.2. Protocol options other than TLSv1.1, TLSv1.2, and TLSv1.3 will be ignored.

The .NET Open Client StrictHostVerify property on both the RuntimeProperties and Connection classes has been marked as Obsolete. This property and its associated behavior are ignored and do not affect the HTTP host name validation performed by .NET Open Client. The hostname validation for .NET Open Client HTTPS connections relies on the underlying .NET implementation for its behavior.

TCMAN and PASMAN are command-line utilities used for managing and administering PASOE. They support three types of actions: manager, server, and general, as described in the Learn about PAS for OpenEdge administration tools.

Configuring HTTPS for Manager Actions

When using an HTTPS port for a PASOE instance, manager actions require that the Java Trust Store contains the appropriate root certificates. Unlike other administration tools, these actions do not use the %DLC%/certs store.

Steps to Configure Java Trust Store

Below are steps that work for most Java installations when using PASOE default certificates. Similar procedures can be followed for self-signed and CA-signed certificates.

1. Add Root CA to the Java Trust Store

   To use the default certificates provided with PASOE, run the following command to add the corresponding root CA to the Java Trust Store.

   Start the proenv environment with elevated user permissions (root/Administrator), then use:

   Linux:

    $JAVA_HOME/bin/keytool -import -trustcacerts -alias <alias_of_your_choice> -file $DLC/certs/506395dd.0 -keystore $JAVA_HOME/lib/security/cacerts -storepass changeit

   Windows:

   "%JAVA_HOME%\bin\keytool.exe" -importcert -alias <alias_of_your_choice> -file %DLC%\certs\506395dd.0 -keystore "%JAVA_HOME%\lib\security\cacerts" -storepass changeit

   Note: Ensure that the JAVA_HOME variable points to the same version used by the OpenEdge installation.

   Confirmation Steps:

   • When prompted:

     Trust this certificate? [no]: yes

     Type yes to confirm.
   • If successful, you should see:

     Certificate was added to keystore

2. Validate Hostname Configuration

   For HTTPS communication during manager actions, PASOE utilizes the psc.as.https.nohostverify property, which is set to a default value of “true”:

   This configuration permits testing with the default certificates provided by PASOE. However, in production environments, it is essential to enable hostname verification. This can be accomplished by adding the following property to the catalina.properties file of a PAS instance:

   psc.as.https.nohostverify=false

   This ensures secure HTTPS communication in a real-world deployment.

The SAML client.login.model fails with “java.lang.ExceptionInInitializerError: null”.

Progress Developer Studio for OpenEdge (PDSOE) provides the "Report Technical Issue" feature that enables customers to directly log a support case. This feature depends on a service hosted on a Progress server accessible through the web. Progress has determined that this feature is rarely used. So, it opted to retire the hosted service and remove the "Report Technical Issue" feature from the Developer Studio.

Customers can contact Technical Support through the SupportLink portal or by phone. To get the list of phone numbers by region, browse to the Welcome to SupportLink page and click “Call Support". Then, click the “Call Support” button for OpenEdge.