WhereScape is pleased to announce that WhereScape RED 10.6.0.0 is now available.
This release of RED is compatible with WhereScape 3D 9.0 versions and up.
| Before upgrading, review the Important Messages when Upgrading for more information. |
Go to https://www1.wherescape.com to see available product versions and release notes for older versions.
Log into the WhereScape Support Portal to access downloads.
In this release of RED we have added a new feature enabling Extensible Authentication for Connections in RED. This feature combines connection resilience, authentication scripts and extended RED Profile attributes to create a framework for connecting to systems which require complicated client side authentication workflows not provided directly by their respective ODBC drivers and/or tools.
This feature enables working with authentication workflows such as oAuth 2.0 but also allows a way to pop-out to additional authentication UI's such as for entry of Time-based One-Time Passwords for multi-factor authentication.
This feature is enabled through the following new functionalities of RED for ODBC/Database and Extensible Source Connections:
Two new groups under Advanced Connect Parameters have been added to Connections, all of these session-level fields are in-memory only and can be persisted to your RED Profile between sessions.
Auth Configuration
Auth Tokens
The following changes have been implemented since 10.5.0.0
| JIRA | Release Note |
|---|---|
| RED-12352 | Updated the wsl_scheduler_profile_maintenance script to support the new authentication fields added in 10.6.0.0 |
| RED-12343 | Added Scripted Authentication support to RED UI enabling extensible authentication methods for RED ODBC, Database and Extensible Source Connections |
| RED-12320 | Improved performance of opening object properties on large repositories. |
| RED-12302 | Added support to the RED Scheduler Plugin to support the new authentication tokens and connection string expansion added in RED 10.6.0.0, additional fields have been added to redadmin.ws_scheduler_profile to securely store these tokens. |
| RED-12092 | Improved performance of the RED Metadata by adding indexes to support the common metadata join patterns throughout the product. |
| JIRA | Release Note |
|---|---|
| RED-12361 | Fixed an issue where creating deployment applications via the command line was broken in 10.5.0.0 |
| RED-12347 | Fixed a 3D export to RED issue where Named Targets; SQL Server, Oracle and Teradata were unable to be resolved during deployment. |
| RED-12328 | Fixed a RED Metadata syntax issue which caused update failures during manual alterations of Index Objects in RED, affecting PostgreSQL versions 15+ |
| RED-12322 | Deleting jobs via application deployment will now trigger the scheduler integration script to remove the job from Azkaban. |
| RED-12314 | The new 'execute-script' method of scheduler-util.jar is now thread safe when running in multi-threaded jobs. |
| RED-12309 | The RED feature in Azkaban to execute a kill script in case of a job being manually aborted now inherits the JRE from the parent process, avoiding the need to have java on the system path. |
| RED-12308 | Resolved a RED Scheduler Plugin issue where replacements of Extended Properties via the token format $WSL_EXP_<property_name>$ were not working |
| RED-12295 | Fixed and issue where Application Deployment of Jobs was not setting the credentials for the Scheduler REST API, causing publishing of deployed jobs to fail. |