Known issues in OpenEdge 12.8.12
- Last Updated: October 29, 2026
- 1 minute read
- OpenEdge
- Documentation
Click here for a list of the fixed issues.
The following table lists the release notes in this release.
| Component | Issue Number | Description |
|---|---|---|
| Lang | OCTA-52510 |
Summary
In prior releases, HttpClient performed hostname verification only after the handshake (HostnameVerificationPolicy.CLIENT). The certificate must now satisfy both checks for the connection to succeed.
This change affects environments where:*
Affected OpenEdge components:
Recommended Action Ensure that all target server certificates include SAN DNSName entries that match the hostname used in the connection URL. Certificates issued by public Certificate Authorities since approximately 2017 typically include proper SAN entries and require no changes. |
| Lang | OCTA-84444 |
A bug introduced in OpenEdge 12.3 caused ABL indeterminate arrays that are initialized with constant values to give an incorrect value for the EXTENT() function. This issue affected ABL programs that declare an indeterminate array variable using the EXTENT keyword without specifying a size and initialize it with a list of constant values (e.g., DEFINE VARIABLE myArr AS INTEGER EXTENT INITIAL [1, 2].), and this DEFINE comes after a statement that causes the execution of the EXTENT() function. In affected versions, the extent of such arrays was not correctly determined at compile time, resulting in incorrect runtime behavior. This issue is resolved in 12.8.12 and 13.1. Recompilation is required for any ABL program that declares indeterminate arrays initialized with constant values. Programs that use determinate arrays (where the extent size is explicitly specified) do not require recompilation. This fix introduces a minor r-code version change for ABL code that contains indeterminate LONGCHAR arrays where any element is initialized with the UNKNOWN value (?). R-code compiled with this fix cannot run on OpenEdge 13 releases earlier than 13.1, or on OpenEdge 12 releases earlier than 12.8.12. |
| Lang | OCTA-97794 |
Starting in OpenEdge 12.8.12, |
| PASOE | OCTA-89047 |
This release upgrades the bundled Apache Tomcat to version 10.1.56. In this version, the HTTPS Connector attribute To retain previous behavior, you may set |
| PASOE | OCTA-102940 |
Starting with OpenEdge 12.8.12 (and carried forward into 13.1), JWT authentication using the HS512 signing algorithm now enforces the HMAC-SHA512 minimum key length requirement: the signing secret must be at least 512 bits (64 bytes) long. Previously, OpenEdge did not enforce this minimum, so shorter secrets that had been working on earlier releases (e.g. 12.8.6) would authenticate successfully. After upgrading, JWT authentication attempts using a secret shorter than 64 bytes now fail with an error indicating the secret length for HS512 must be at least 512 bits. This is an intentional security hardening change, not a defect. Administrators who use JWT authentication with HS512 must ensure their signing secret is at least 64 bytes (512 bits) long after upgrading. See KB article: https://community.progress.com/s/article/can-t-authenticate-using-jwt-after-upgrading-to-12-8-12 |
| PDSOE | OCTA-96879 |
In OpenEdge 12.8.11, 13.0, and later versions, users may see a Windows Defender exclusion prompt when launching Progress Developer Studio for OpenEdge (Developer Studio) on Windows systems with Windows Defender real-time protection enabled. This prompt was introduced with the upgrade to Eclipse 4.34. Previously, no Windows Defender prompt appeared at startup. Now, users may see a prompt that allows them to choose one of the following options: Exclude: Excludes the Developer Studio installation directory from Windows Defender scans to improve startup and build performance. However, this exclusion may increase security risk. Continue scanning: Keeps Windows Defender scanning enabled and leaves the existing security configuration unchanged. This behavior originates in the Eclipse platform and is not specific to Developer Studio. Users can review or remove an exclusion at any time from . Reference: Eclipse Windows Defender documentation. |