Platform Server - 11.13.2 

Published on 2021-11-02 10:48:42
PlatformServer-11.13.2 (Build 32392).exe
242.53 MB

Installation Checklist EN
Installation Checklist JP

  • Compatible with Development Environment 11, versions or later.
  • Can be managed by LifeTime 11, Release Sep.2019 or later
Additional Resources For further information on any issues, use the Support Portal.

NOTICE: OutSystems does not give support to any undesirable behavior you may experience due to the use or manipulation of undocumented components of the OutSystems platform, such as, internal JavaScript, RuntimePlatform library, database system meta-model, components in installation directories, etc.
When upgrading the Platform Server from OutSystems 10 to this version, a known issue in the system components installation prevents the upgrade from succeeding. We advise customers upgrading from OutSystems 10 to OutSystems 11 to upgrade first to 11.13.1 or wait for the next release.
Release Notes

New in Platform Server 11.13.2

  • Flexible Upgrades is now available for Platform installations running over Oracle. (R11PIT-315)

Bug Fixing

More details

Fixed an issue in the Users application preventing end-users from logging in when using standard LDAP authentication.
Application Lifecycle Users

Fix Details:
End users configured with standard LDAP authentication were not able to log in due to an "Invalid username or password" error. This was an error in Users application related to the encrypt/decrypt password algorithm. The issue was found in version 11.7.3 and it's now fixed.

Fixed an upgrade schema error when clicking "Create/Upgrade Database" in the Configuration Tool while upgrading the Platform Server from version 10 to version 11.11.1 or later. This issue applies only to self-managed environments.
Infrastructure Management Platform Configuration

Fix Details:
While upgrading the Platform Server component in a self-managed environment from version 10 to version 11.11.1 or later, clicking the "Create/Upgrade Database" button in the Configuration Tool caused the upgrade schema error "Unable to obtain the connection string". Besides blocking the upgrade process, this issue didn't cause downtime or loss of service.

Improved the performance of the modules preparation phase executed during the upgrade process.
Infrastructure Management Platform Configuration

Fix Details:
The module preparation phase after a Platform Server upgrade could take a long time to complete, increasing the time a development team would have to go without being able to publish any modules. This is especially noticeable in large factories and it would only occur in Platform Server 11.12.0 or later. The module preparation was improved to be more performant.

Fixed a high severity vulnerability by upgrading the packaged RabbitMQ to 3.8.21.
Infrastructure Management Platform Configuration

Fix Details:
All versions of RabbitMQ prior to 3.8.16 are prone to a denial of service vulnerability. The packaged RabbitMQ was upgraded. You can check more details in this security bulletin.

Fixed an issue that caused the incorrect calculation of the average time in Service Actions Performance report.
Application Lifecycle Service Center

Fix Details:
The Service Actions Performance report in Service Center showed incorrect values for "Avg. Time". When generating or exporting a Service Actions Performance report from the Analytics tabs of Service Center, the report showed the same value for both "Avg. Time" and "Total Time" columns.

Fixed a malformed login URL for SAML 2.0 when using an external IdP with SSO login URL containing query parameters.
Application Runtime Authentication and Authorization

Fix Details:
After setting up SAML 2.0 in Users, app end users that try to log in get redirected to the User app with a permission denied message. The issue occurred due to a malformed login URL when using SAML 2.0 with a Single Sign-On URL that contained a query parameter.

Fixed an issue that occurred when clicking "Apply and Exit" in the Configuration Tool after changing the Platform, Log, or Session database configurations.
Infrastructure Management Platform Configuration

Fix Details:
Configuration Tool was not respecting alterations to the databases connection details (Platform, Log, and Session). Changes done in the Configuration Tool UI were not effectively saved. Upon clicking "Apply an Exit", older values (for example: database address, authentication mode and credentials) would be used, ultimately causing connection errors or operations to be attempted with the old values. The issue was fixed, and values changed in the UI are now fully respected.

Fixed an issue that might cause the Configuration Tool to lock the Administrator or Runtime Active Directory accounts when using Windows Authentication.
Infrastructure Management Platform Configuration

Fix Details:
When using Windows Authentication, opening the Configuration Tool could lock the Administrator or Runtime user accounts in the Active Directory. This would happen under a strict security policy to lock user accounts on first failed login attempt. This issue occurred because the Configuration Tool was attempting to login to the database with the Administrator and Runtime users as soon as the UI is opened, which doesn't apply to Windows Authentication.

Fixed a licensing query that would generate "Licensing error" entries in Service Center Error logs.
Application Runtime Licensing Runtime Checks

Fix Details:
In Service Center error logs, an entry with the message: "Licensing Error: An error occurred while validating feature 'InternalExternalUsersCounter': ORA-00972" would happen frequently. Appart from log polution, there was no futher impact. It would happen only when all of the following conditions are true:

  • the Platform Server version is 11.11.3 or later
  • the platform database is Oracle 12.1c
  • the license was purchased after January 2020

The issue was fixed in an OutSystems internal query to no longer result in such an error.

Fixed an issue where the Configuration Tool UI was not disabling Log and Session database credential fields when using Windows Authentication.
Infrastructure Management Platform Configuration

Fix Details:
In the Configuration Tool, when authentication is set to Windows Authentication on the Platform tab, login errors could occur. The Administrator, Runtime, and Session credential fields in the Log and Session tabs should be disabled. The issue would cause the fields to be editable. This would force the user to fill in those fields, and, when the credentials didn't match, would cause a login error.

Fixed a compilation issue when consuming a SOAP Web Service containing a type and a subtype with the same name.
Application Runtime Logic Execution

Fix Details:
A compilation error occurred after publishing a module which consumed a SOAP Web Service with polymorphism. This only occurred when one of the possible subtypes declares an anonymous type with the name as the subtype.