Domino 4.6.4 (March 2022)

This release provides container security patches.

Keycloak is upgraded to version 15.1.1.

Fixed a bug that allowed project collaborators with Launcher User or Results Consumer permissions to access the project’s files.

Fixed an issue in Domino 4.6.2 and up that prevents all new executions from starting when a project directory name is empty or contains the slash character.

Dataset snapshot creation no longer gets stuck in a "Pending" state when the dataset contains a directory with an all-numeric name.

Opening an un-cached workspace no longer causes the workspace to get stuck in the "Pulling" status.

Fixed a bug that prevented some Kubernetes pods from starting up in air-gapped network environments.

When upgrading from Domino 4.x to 5.1, Domino does not correctly handle environment revisions that have both a Docker image and a base environment revision. This issue is resolved in Domino 5.2.0.

Sync operations for deployments backed by SMB file stores can sometimes result in unintended file deletions. This issue is fixed in Domino 5.2.0.

You cannot delete a .gitignore file in a Domino File System (DFS)-based project. This issue is fixed in Domino 5.2.0.

Apps may fail with unusual error messages. This issue is resolved in Domino 5.2.0.

When an API key explicitly passed as an api_key argument and the DOMINO_TOKEN_FILE environment variable is set, Domino uses the token authentication. This issue is resolved in Domino 5.2.0.

When Flask apps generate links, this can result in unwanted 302 redirect behavior. This issue is fixed in Domino 5.2.0.

When a Model API fails while retrieving files from git using SSH keys, the private key and the key password, if any, may be exposed in the Domino log. This issue is resolved in Domino 5.2.0.

The Import Project drop-down does not display projects owned by organizations of which you are a member. This issue is resolved in Domino 5.2.0.

When starting a workspace, the application sometimes gets stuck in the Pulling status, even though the logs indicate that the workspace started successfully. If this occurs, stop and start the workspace again. This issue is fixed in Domino 5.2.0.

After upgrading to 4.6.4 or higher, launching a job from a Git-based project that uses a shared SSH key or personal access token results in a Cannot access Git repository error.

In a Git-based project, requirements.txt must be in your project’s Artifacts folder in order to be picked up by an execution, instead of at the root level in your project files.