eclipse-che/che 7.79.0

Eclipse Che 7.79.0

on GitHub

Major Enhancements

Administrators can specify which users and groups are authorized to use Eclipse Che

In this release, new properties for advanced authorization have been added to the Custom Resource:

AllowUsers []string `json:"authorizedUsers,omitempty"`
AllowGroups []string `json:"authorizedGroups,omitempty"`
DenyUsers []string `json:"unauthorizedUsers,omitempty"`
DenyGroups []string `json:"unauthorizedGroups,omitempty"`

The new configuration allows setting up granular access for different groups and users:

 networking:
    auth:
      advancedAuthorization:
        allowUsers:
          - user-a
          - user-b
        denyUsers:
          - user-c
        allowGroups:
          - team-a
          - team-b
        denyGroups:
          - team-c

Users who are not allowed will see the following warning when trying to access the User Dashboard:

N.B. AllowGroups and DenyGroupsproperties are only supported on OpenShift.

Eclipse Che local development experience with IntelliJ IDEA

Initial support of the local desktop development using IntelliJ Thin Client connected to a remote DevWorkspace is now available:

Support multi-arch builds in next-build GH Workflow for DevWorkspace Operator

DevWorkspace Operator is now being built for the following platforms: linux/amd64, linux/arm64, linux/ppc64le and linux/s390x.
The related multi-arch images are available at:

• quay.io/devfile/devworkspace-controller:next
• quay.io/devfile/project-clone:next
• quay.io/devfile/devworkspace-operator-index:next
• quay.io/devfile/devworkspace-operator-index:next-digest
• quay.io/devfile/devworkspace-operator-bundle:next
• quay.io/devfile/devworkspace-operator-bundle:next-digest

Support for VS Code Extension services, such as Ansible Lightspeed, that use the OAuth authorization flow

OAuth2 authorization code flow using Callbacks and URI handlers is now supported, and Visual Studio Code Extensions that use this flow will work in the Eclipse Che workspaces. For instance, users of the Ansible VS Code extension can use its AI-powered Lightspeed service.

N.B. The Ansible VS Code Extension issue currently prevents the extension from working on remote development environments.

Major Bug Fixes

New projects are lost after a workspace restart

Before this release, VS Code launcher was adding projects from the devfile to .vscode-workspace configuration file only during the initial workspace startup. However, if a new project (or dependent project) was added to the devfile.yaml, and the workspace was restarted using the Restart Workspace from Local Devfile, the new project was not added to the .vscode-workspace configuration file, and the user was not able to see it in the VS Code, although all the projects were cloned in /projects folder. The defect has been fixed in this release and now the projects are correctly updated in the .vscode-workspace configuration file.

Bitbucket OAuth 1.0 is not displayed on Git Services tab

Bitbucket OAuth 1.0 is now correctly displayed on the 'Git Services' Tab of the User Dashboard: