Digital.ai Deploy 22.2.x Release Notes
Digital.ai Deploy 22.2.0
Digital.ai Deploy 22.2.0 includes the following new features:
- Enable Profiling Logs for SQL Queries
- Operator-based installer—install Deploy in a Custom Namespace
- Additional parameters in OIDC configuration
And more bug fixes and enhancements.
Support Policy
See Digital.ai Support Policy.
Upgrade Instructions
The Digital.ai Deploy upgrade process you use depends on the version from which you are upgrading, and the version to which you want to go.
For detailed instructions based on your upgrade scenario, refer to Upgrade Deploy.
Digital.ai Deploy 22.2.0 New Features
Here's what is new with Digital.ai Deploy 22.2.0.
Enable Profiling Logs for SQL Queries
-
Profiling can be enabled in Deploy which lets you log query details such as query parameters and time taken by a query to the
XL_DEPLOY_SERVER_HOME/log/profiling.logfile. -
The
XL_DEPLOY_SERVER_HOME/log/profiling.logfile is rotated the same way as other log files are.
For more information, see Enable Profiling Logs for SQL Queries.
Operator-based installer—install Deploy in a Custom Namespace
Installing Digital.ai Deploy in a custom name space is one of the salient cloud-native features added to Digital.ai Deploy 22.2. You can now install Digital.ai Deploy in a custom namespace if:
- You would like to install multiple Deploy instances on the same cluster.
- You do not want to install Deploy in the default namespace: digitalai.
For more information, see: Install Deploy in a Custom Namespace.
Additional Parameters in OIDC Configuration
You can now send additional parameters to the OIDC provider as part of the OIDC authentication request.
Here's an example, in which you can find two additional parameters—param1 and param2.
deploy.security:
auth:
providers:
oidc:
clientId: "<Your client ID>"
clientSecret: "<Your client secret>"
clientAuthMethod: "<Your client authentication method here>"
issuer: "<Enter the Open ID Provider Issuer>"
keyRetrievalUri: "https://oidc.example.com/endpoint/keys"
accessTokenUri: "<The redirect URI to use for returning the access token>"
userAuthorizationUri: "<The authorize endpoint to request tokens or authorization codes via the browser>"
logoutUri: "<The logout endpoint to revoke token via the browser>"
redirectUri: "https://xl-deploy.example.com/login/external-login"
postLogoutRedirectUri: "https://xl-deploy.example.com/login/external-login"
idTokenJWSAlg: "<The ID token signature verification algorithm>"
rolesClaimName: "<Your roles claim>"
userNameClaimName: "<Your username claim>"
additionalParameters:
param1: false
param2: "str"
With such a configuration, the additional parameters are passed in the login URL as shown in the following example request URL.
https://example.oktapreview.com/oauth2/.../.../code_challenge=xyz¶m1=false¶m2=str
Version Upgrades
Supported Databases
Deploy 22.2 supports the following databases.
| Database | Versions Supported | |-----------------------|----------------------------| | PostgreSQL | 13.6 and 14.2 | | MySQL | 5.7 and 8.0 | | Oracle | 12c and 19c | | Microsoft SQL Server | 2017 and 2019 | | DB2 | 11.1 and 11.5 |
Deployment API Performance Improvements
Deploy 22.2 brings you a series of performance improvements around deployment APIs.
Plugins and Integrations
Bug Fixes and Field Incidents
Bug Fixes and Field Incidents—22.2.0
- D-18895 - Fixed a user session expiry issue for deleted users. The user session of a deleted user expires as soon as you delete the user.
- D-18894 - Fixed an issue after which only users with the Report-View permission are able to download the generated report.
- D-20538 - Fixed the deadlock issue with the Lock plugin.
- D-20857 - Fixed an issue with the permissions service REST API results, which were returning all configuration items instead of the folders.