Known issues in OpenEdge 12.8.2

With the release of the Progress.Collections.HashMap in OpenEdge 12.7 there was a need to re-examine the offerings from the OpenEdge.Core library. In the OpenEdge 12.8 release several base classes have been updated to ensure they are compatible with the Progress.Collections.HashMap through implementation of the IHashable interface. This adds to the previous but unannounced capability to support the Progress.Collections.SortedSet, also available in these same classes.

• OpenEdge.Core.DateHolder
• OpenEdge.Core.DateTimeHolder
• OpenEdge.Core.Decimal
• OpenEdge.Core.EncodedString
• OpenEdge.Core.FileInfo
• OpenEdge.Core.Integer
• OpenEdge.Core.LogicalValue
• OpenEdge.Core.Memptr
• OpenEdge.Core.ByteBucket
• OpenEdge.Core.SemanticVersion
• OpenEdge.Core.String
• OpenEdge.Core.TimeStamp
• OpenEdge.Core.WidgetHandle
• OpenEdge.Core.Util.Token.cls

As part of the ability to support these new collections classes, the OpenEdge.Core.Collections.StringStringMap and OpenEdge.Core.Collections.StringKeyedMap classes have been retrofitted to make use of the new Progress.Collections.HashMap built-in object, rather than reliance on static temp-tables which were used for the initial implementation. A new class OpenEdge.Core.Collections.HashMap was also introduced as a more direct implementation of the ProgressCollections.HashMap while remaining compatible with other OpenEdge.Core.Collections classes though this drops some behavior offered by OpenEdge.Core.Collections.Map through its use of a temp-table for storing the key and value objects.

Behavior Change: Processing of errors in a Business Entity now throws error object with multiple error messages. In previous versions, an object with only the first error message was being thrown.

Startup parameters -minport and -maxport are used to specify the lowest and highest port numbers in a specified range of port numbers accessible to a client.

Starting with OpenEdge 12.8, the default values for -minport and -maxport have been changed for Unix systems only. This change was introduced due to the increased number of ports registered with the IANA in the original default range.

OLD default values:

-minport 1025

-maxport 2000

 

NEW default values:

-minport 12000

-maxport 13000



Note: This applies to Unix systems only (the Windows defaults will remain the same)

Support for the smaller database block sizes, 1024 and 2048 kilobytes, is deprecated in OpenEdge 12.7.  This applies to creating a new database and starting up existing databases. 

 To determine if you are affected by this:

• * The larger sizes, 4096 and 8192, were introduced in Progress V8.2.  The defaults were changed early in OpenEdge 10.x to 4096 for Windows and Linux.
• Identify your database block size using PROUTIL DESCRIBE and locate the Block Size in the output.
• To change the database block size you must perform a DUMP of the data and LOAD it into a database with a new structure. This can be done with your current version of OpenEdge. 

When existing databases with the smaller block sizes are recreated with a larger block size they experience less system paging.  They also can take advantage of features only available with the larger block sizes, for example large index key entries.

The fix for OCTA-52510 removes the behavior of Java Open Client which previously skipped the PKI chain validation for the OpenEdge supplied certificates even if the server’s certificate is removed from the Open Client application’s certificate store. Java Open Client performs the PKI chain validation for all certificates, including the default server certificates shipped by OpenEdge. The Java TLS implementation used by Open Client client validation logic now requires all server certificates to be properly signed and the server’s certificate chain to be available in the certificate store used by the Java Open Client application.

Java open client will no longer connect to a PASOE server using HTTPS if the PASOE instance is configured to use the default server certificate and the default certificate is not available.

This change is likely to impact Java Open Client applications in development environments and production applications that rely on the convenience of the default configuration.

The fix for OCTA-52510 removes the behavior of .NET Open Client that had skipped the PKI chain validation for the OpenEdge supplied certificates. .NET Open Client now performs PKI chain validation for all certificates, including the default server certificates shipped by OpenEdge. .NET Open Client relies on the built-in TLS implementation that is built-into the .NET runtime for HTTPS connections to the OpenEdge application server. The TLS implementation validation logic requires all certificates presented by a server be properly signed and the complete certificate chain for the the server certificate be available.  Additionally the ROOT certificate must be installed into the ROOT certificate trust store for the platform.

.NET Open Client will not be able to connect to a PASOE server using HTTPS if the PASOE instance is configured to use the PASOE server certificate that is configured by default for convenience because it will fail server validation if the host name is verified. The default PASOE server certificate must be replaced with a valid server certificate and the ROOT signing certificate must be installed onto the machine of the .NET Open Client application. It is not necessary to have a paid server certificate installed. A self-generated ROOT CA that is installed in the ROOT Certificate store may be used as long as the root’s private key is properly protected. In either case, the ROOT certificate must be installed into the ROOT certificate store.  

This change is likely to impact .NET open client applications in development environments and production applications if they rely on the convenience of the default configuration.

Starting with OpenEdge 12.7, when an exception is thrown in .NET Open Client performing a request against the application server, the parameter configuration stored in the ParamArray object are no longer reset if the values remain unmodified from their original assignment prior to executing the application server request.

You can return the old behavior by assigning the InputErrorResetPolicy and/or OutputErrorResetPolicy properties of the ParamArray to RESET_ALWAYS. For more details see the documentation regarding error handling with .NET Open Client.

In OpenEdge Management(OEM)/OpenEdge Explorer(OEE) 12.8 version, configuring database replication properties does not work as the hyperlinks to edit configuration properties are missing when the Database replication is enabled on a Linux platform. Adding Replication Plugin details in ${DLC}/properties/AdminServerPlugins.properties file addresses this problem as a workaround solution. This problem doesn’t exist when OpenEdge Management(OEM)/OpenEdge Explorer(OEE) 12.8 is installed on a Windows platform.

Execute below steps for workaround solution:

• Execute below command from proenv: proenv>mergeprop -action update -delta ${dlc}/properties/merged/replication.delta -type plugin -target ${dlc}/properties/AdminServerPlugins.properties

• Stop admin server and start it. proenv>proadsv -stop
  proenv>proadsv -start

In Progress OpenEdge 12.8, agent as client run with TLSv1.3 to SOAP out call can sometimes timeout or result in an ABL session going down. As a workaround if you experience this scenario, either disable session resumption with TLSv1.3 or use TLSv1.2 protocol

In Progress OpenEdge 12.8, sslc command helps you to get more details about Providers loaded from OpenSSL 3.1. Launching sslc command outside of proenv environment fails with error or it may respond details only for default provider. Progress recommends you to run sslc within the proenv environment to take it’s full advantage.

In OpenEdge 12.8, the encryption and decryption algorithm for \webapps\ROOT\WEB-INF\adapters\rest\runtime.properties file has been replaced with a much more secure and robust algorithm. This is to ensure the utmost protection of the passwords stored on the disk. The OpenEdge used to support “PBEWithMD5AndDES" algorithm which has been replaced with more secured encryption algorithm "PBKDF2WithHmacSHA256" and "AES/GCM/NoPadding”.

Any of the earlier saved encrypted passwords in that file need to be replaced with the newly encrypted passwords, otherwise the earlier ones won’t work in OpenEdge 12.8 release. Once you insert the plain password in this file, it will be automatically encrypted and will be saved in the same file.

Webclient codebases can no longer be installed for appserver using SSL if the default test certificate or a certificate with an invalid hostname is used. Currently -nohostverify behavior can not be enabled when codebase files are being downloaded for an OE appserver.

A nonadmin user can start an uninstall for webclient that an administrator installed but this will break running webclient application an administrator installed as nonadmin user and will not really uninstall webclient.

Webclient version and bits are not displayed in "Add or remove programs" when installed by a nonadmin user.