Skip to content

Releases: DSD-DBS/capella-collab-manager

v4.4.0

20 Sep 11:59
7e18c2d
Compare
Choose a tag to compare

What's Changed

We want user feedback! This release adds a feedback dialog that periodically asks users for feedback (at interval, during sessions, after session termination or via a button in the footer). The feedback is sent via email to registered feedback recipients, so SMTP setup is required.

Full Changelog

Features

Bug Fixes

Documentation

Internal Changes

Full Changelog: v4.3.1...v4.4.0

v4.3.1

17 Sep 16:04
e4b9f6b
Compare
Choose a tag to compare

What's Changed

Features

Bug fixes

Internal changes

Full Changelog: v4.3.0...v4.3.1

v4.3.0

12 Sep 15:32
9ff8225
Compare
Choose a tag to compare

What's Changed

This release contains a long-awaited feature to rename and delete TeamForCapella instances. There are also many smaller UI tweaks such as a more modern icon set and a redesign of the TeamForCapella instance configuration.

Full changelog

Features

Bug fixes

Internal changes

Full Changelog: v4.2.1...v4.3.0

v4.2.1

10 Sep 09:45
83cf867
Compare
Choose a tag to compare

What's Changed

Features

Documentation

  • docs: Add troubleshooting for slow Capella and unresponsive Xpra by @MoritzWeber0 in #1750

Bug fixes

Internal changes

Full Changelog: v4.2.0...v4.2.1

v4.2.0

04 Sep 13:46
3456c6e
Compare
Choose a tag to compare

What's Changed

This release allows communication between sessions of the same user. This can be used to automate tasks between sessions, such as talking to a Capella session from Jupyter.

Full changelog

Features

Bug fixes

Documentation

Internal changes

Full Changelog: v4.1.0...v4.2.0

v4.1.0

13 Aug 12:42
deeacd1
Compare
Choose a tag to compare

What's Changed

Projects in the project overview are now sorted alphabetically and there a new search function. In addition, the login / authorization view was redesigned.

Full changelog

Features

Bug fixes

Internal changes

New Contributors

Full Changelog: v4.0.0...v4.1.0

v4.0.0

31 Jul 15:51
6a52fd1
Compare
Choose a tag to compare

What's Changed

In this release, we've improved some logic around authentication. The previous authentication providers oauth and azure have been removed. Instead, we added support for OpenID Connect including it's security features like state, nonce and PKCE. We have also changed the implementation so that cookies are used for authentication of the frontend.

The new changes might be incompatible with your identity provider if it doesn't have support for OpenID Connect. We have that covered and in this case Keycloak can also be used as middleware. A documentation is available here.

Please read the "Breaking Changes" section carefully. You have to update the values.yaml before this update.

Breaking Changes

For Administrators

  • Support for non-compliant OIDC identity providers has been removed. If you've used OAuth without OIDC before, you can set up Keycloak as intermediate identity provider. More information here.
  • Since we no longer distinguish between different identity implementations, we have removed the providers abstraction in the values.yaml. This means that the providers field that supported azure or oauth as values has been removed and instead of oauth.xy or azure.xy xy is used directly (e.g. instead of oauth.endpoints.wellKnown it's endpoints.wellKnown).
  • The OIDC well-known endpoint is now a required configuration value and must be defined in endpoints.wellKnown. As a result of reading all endpoints from the well-known endpoint, the endpoints.token_issuance endpoint has been removed. The endpoints.authorization endpoint can still be used to overwrite the authorization endpoint from the well known configuration. It's needed for the OAuth mock, in most of the cases you can omit it.
  • The usernameClaim configuration was removed. Instead, a more fine-grained mapping is available. If you want to have the same behaviour as it was before the update, set idpIdentifier and username to the previous value of usernameClaim.
    claimMapping:
        idpIdentifier: sub # Maps the `sub` attribute in the JWT to the `idpIdentifier` attribute in the CCM. `idpIdentifier` is a new attribute to identify users uniquely. The attribute can be patched via the API for existing users.
        username: preferred_username # The username which is displayed in the UI and can be used to add users to projects.
        email: email # Optional email address.
  • Only relevant if you use the image-builder or k8s-deploy Gitlab CI/CD templates for the deployment of the Collaboration Manager: The unencrypted suffix of keys was removed from the SOPS encrypted files. In addition, the general.values.yaml and secret.values.yaml were merged into one encrypted file values.yaml. in both cases it's recommended to use the encrypted_regex configuration of SOPS instead. More information about the new setup here: image-builder / k8s-deploy

For API Users

  • The PATCH /api/v1/users/{id}/roles route has been removed. Use the new PATCH /api/v1/users/{id} route and pass the new role as attribute in the payload.
  • The POST /api/v1/users endpoints requires a new attribute idp_identifier in the payload.
  • The GET /api/v1/sessions/{session_id}/connection returns the cookies as header (Set-Cookie) instead of an attribute in the payload.

Full changelog

Features

  • feat!: Replace bearer with cookie-based authentication by @dominik003 in #1587

Documentation

Internal changes

Full Changelog: v3.5.0...v4.0.0

v3.5.0

25 Jul 18:32
f366ae0
Compare
Choose a tag to compare

Important

The upcoming database migration will fail if there are multiple users with the same username but different casing! Scan your users list to remove duplicated users before updating.

What's Changed

Features

Documentation

Internal changes

Full Changelog: v3.4.0...v3.5.0

v3.4.0

23 Jul 19:20
448e14b
Compare
Choose a tag to compare

Notable changes

We started using Grafana alerts to notify system administrators of unexpected application and session states. For the beginning, there will be alerts about unhealthy sessions and failed jobs. The change may result in duplicated data sources in your Grafana instance. More information here: #1661

What's Changed

Features

Bug fixes

Development

Full Changelog: v3.3.0...v3.4.0

v3.3.0

11 Jun 20:05
2a6e31c
Compare
Choose a tag to compare

Notable changes

In this version, it's possible to share sessions with other users for better collaboration. Once enabled for a specific connection method, it's possible to enter usernames to share the session with. For the beginning, sharing is supported for Jupyter and Xpra.

To enable session sharing, follow the those steps as administrator (as user, no additional action is required):

  • Enable the sharing flag in the tool configuration for the supported connection methods (Xpra & Jupyter)
  • Append &sharing=1 to the redirect URL for the Xpra connection method.

What's Changed

Features

Bug fixes

Documentation

Internal changes

Full Changelog: v3.2.9...v3.3.0