Unlock user accounts
The Users page now displays information about whether users are activated or locked. Additionally, administrators can now unlock users without changing their passwords.
Upload a logo
Administrators can now configure a logo image and website icon for their tenant/company within .
JWT authentication support for APIs
Added OAuth2.0 JWT authentication support for APIs as an alternative to basic authentication.
Key and secrets management
The system now supports access to the AWS Secrets Manager for connection parameters and credentials in Data Store (Database) stages and the Execute Query in DB analysis node. In a single-tenant installation, the Secrets Manager access may be to another AWS account. Secrets are referred to with a value like sec(your_secret_name) or sec(your_secret_name field_in_secret). Execution parameters or environment properties may specify a secret reference, and may themselves be encrypted, when those properties are used in Data Store (Database) stages or in the Execute Query in DB analysis node.
Analysis execution parameters
The analyst defining an Analysis stage can now specify execution parameters that must be supplied when running the analysis. These parameters can also be input when testing the analysis interactively, or accepting changes on the nodes of the analysis. This allows the analyst to avoid using "hard coded" values during analysis design, and ensure that the appropriate execution parameters are supplied when executing the stage.
Encrypt execution parameters
When executing a data stage, you can now specify execution parameters as encrypted values. These values are shown only as a full mask (*****) on the page. Output parameters defined in process models can also be defined as encrypted values. This enables you to encrypt the credentials that are passed into your process models, and also hides these values from the execution history.
Azure Postgres Flexible Server database
New Azure installations for release 11.2 create a Postgres Flexible Server database. Infrastructure upgrades from earlier releases will migrate the Postgres Single Server database to Flexible server. Review the Azure installation guide for single server backup and flexible server restore steps when upgrading.
Other changes
- JVM options to increase the Java stack size have been added to the Enterprise installation to reduce possible errors with the use of certain nodes in the analysis designer.
- The AWS single-tenant edition can now be configured to access a separate KMS endpoint for using a customer managed key to encrypt/decrypt data values in Data360 DQ+.
- To improve application availability, the Execute Query in DB node now requires a Sample SQL query definition where you must specify a query that will return a modest amount of data for interactive analysis building.
- The Analysis Settings dialog has been rearranged to move execution profile settings to a separate tab for greater consistency with the same sorts of settings on other stages, such as Data Views. The System tab of the Data View stage has been renamed to Execution Profile.
-
Added support of stage UUID as an alternative to stage ID in APIs for querying stage data. The affected APIs include:
queryActivityLogData(),queryCaseStoreData(),queryDataStoreData(), andqueryDataViewData(). - The commons-text library used for enterprise CDP executions has been upgraded to address security concerns.
- The size of the KEYDATA column in the CAF_SECDATAKEY table has been increased from 512 characters to 1000 characters to support larger key sizes. See the installation guide for upgrade SQL statements to perform.