Known issues in OpenEdge 12.8.4

For multi-tenant and partitioned tables, the _Event-Context field of the _Aud-audit-data records for audit event IDs 5100, 5101, and 5102 was missing the tenant or partition identifier. Without this information, it is sometimes impossible to identify which record was changed. The _Event-context field for audit records of these policies will display this information using the partition identifier instead of the name used for auditing events of other policies. For multi-tenant tables, this partition identifier can be mapped to the tenant or group using the _Tenant and _Partition-Set tables. For table partitioning, the identifier can be mapped to the partition through the _Partition-Policy-Detail table.

Starting with OpenEdge version 12.8.4, Update releases are only delivered as an incremental installation which means that a previous version of 12.8 must be installed before running the 12.8.4 installer. A full installation is not available in OpenEdge version 12.8.4.

OCTA-69451

When the timeout for a stop-after is exceeded, a StopError object can leak when garbage collection runs while STOP-AFTER is in effect. For the HttpClient in particular this may be reported as a ByteBucket leak when tracking DynObjects through use of the OpenEdge.Core.Util.LeakCheck class or FindLeaks.p script from Progress Tech Support. This is a known issue and is in our backlog for future consideration.

In order to enable the fix for OCTA-51154, you must re-compile classes that have THIS-OBJECT references to class properties and variables.  

PASOE SOAP support deployment for both Windows and Linux, has changed. Newly created SOAP services will properly deploy using the new script. IA copy of the deploySOAP.[sh|bat] script from $CATALINA_HOME/bin is properly tailored and copied to $CATALINA_BASE/bin. $CATALINA_HOME is $DLC/servers/pasoe while $CATALINA_BASE is your instance directory. When creating a new instance, the tailoring procedure modifies the scripts to set the CATALINA_HOME and $CATALINA_BASE values. 
Existing SOAP deployment instances are not automatically updated and might not start. If you are unable to deploy existing SOAP services, copy the deploySOAP.[sh|bat] script from $CATALINA_HOME/bin to $CATALINA_BASE/bin. $CATALINA_HOME is $DLC/servers/pasoe while $CATALINA_BASE is your instance directory. It is necessary for you to manually update deploySOAP.[sh|bat] script and set both $CATALINA_HOME and $CATALINA_BASE to match your configuration:
deploySOAP.sh:   set CATALINA_BASE (line 100), CATALINA_HOME (line 130)
deploySOAP.bat: set CATALINA_BASE (line 32),  CATALINA_HOME (line 31)

An upgrade of Spring Security 6.x changed the way Spring Security manages ABL web application (oeab ) login session management. The change results in the OERealm Authentication Manager to insert a zero login session id into the Client-Principal’s session id attribute. This means a form-based login will not include the client login session id as it did before.
A new property OERealm.AuthProvider.genInternalSession has been added to solve other Client-Principal session id issues. If your application depends on a unique identifier for the Client-Principal’s session id, you can set this property to true to assign a unique value (GUID). Note: This is not the same as the client login session id.

The installation of the ESBAdapter is not updating configuration files properly. This means that the ESB Adapter integration will not run properly and an error will be seen. To workaround this issue, please do the following steps:
Step 1. Please capture value(s) of the following key(s) from  $DLC/sonic/ESB10.0/config/installtlr.properties.
Copy the values of szSonicContainerName, szSonicDomain, szSonicPassword, szSonicUrl, szSonicUsername and szPathToSonic
Step 2. Edit $DLC/install/tlr/installtlr.properties to match the values captured in step 1. Set the values for szSonicContainerName, szSonicDomain, szSonicPassword, szSonicUrl, szSonicUsername and szPathToSonic.
Step 3. Run the script file from $DLC/sonic/ESB10.0/config directory: offline.bat (for Windows) or offline.sh (for Linux) file.
Step 4. (Optional) Validate that the values were properly applied in the $DLC/install/tlr/esbadaptertlr.log file.