Neptune DXP - Open Edition 23.10.6 release notes

This information is especially important for you if you have already downloaded Neptune DXP - Open Edition 23.10.6, and you use Microsoft SQL Server as the database for your Neptune DXP - Open Edition installation. Neptune DXP - Open Edition 23.10.6 introduces improved behavior for setting the default value of Boolean fields in the Table Definition tool.

Unfortunately, this causes an unforeseen side effect: After installing Neptune DXP - Open Edition 23.10.6, it is not possible to update table definitions that have been created with Neptune DXP - Open Edition 22 and have a default constraint for Boolean values. This only applies when MS SQL Server is used as a database.

Therefore, Neptune DXP - Open Edition 23.10.6 is no longer available for download and is superseded by the patch release Neptune DXP - Open Edition 23.10.7, which includes all the changes mentioned below.

Customers who have already upgraded to Neptune DXP - Open Edition 23.10.6 must upgrade to patch release Neptune DXP - Open Edition 23.10.7 immediately.

Cockpit

Feature: You can sign out from an external identity provider (IdP) when signing out from a launchpad and/or signing out from the Cockpit
Fix: Use correct endpoint when fetching versions

App Designer

Fix: Binding a property of an object with a data source or model path binding no longer clears those values
Fix: Custom components with renamed properties now correctly apply formatters bound to those properties
Fix: Changed objects are now correctly marked as changed

Table Definition

Fix: We improved the behavior for setting the default value of Boolean fields

Mobile Client

Fix: We ensured that active version returns a string, instead of an array

Proxy Authentication

Feature: Allow encryption of OAuth 2.0 headers, as well as general headers

Certificates

Enhancement: The private key is only visible once after creating the certificate

Back end/Misc

Enhancement: For SAML authentication, if the issuer is not set as the URL, determine the SAML protocol using the login URL
Enhancement: You can enable restricted proxy in settings. This ensures that the proxy only allows pre-approved URLs that have already been defined in an API, OData, or Remote System.
Fix: JWKS proxy property fixed for JWT type authentication