1.4.0-beta1

What's Changed

• Introduces a trusted network model (Web of Trust) allowing user-verifiable trust chains (#281)
• Provides a new role (create-vaults) configuration option that allows granular control over vault creation permissions (#296)
• Update Keycloak to 25.0.6
• Introduce CHANGELOG file

Full Changelog: 1.3.4...1.4.0-beta1

Important Considerations for the 1.4.0 Update

1. Optionally configuring Web of Trust Parameters

With Web of Trust (WoT), two new configuration options are now available:

• wot_max_depth (default: 3): Defines the maximum number of graph edges between two users to establish a trust chain.
• wot_id_verify_len (default: 2): Sets the required number of characters to be entered during user fingerprint verification.

Note: Currently, both of these parameters can only be modified within the database. A future update will introduce user-friendly configuration options (see Issue #297).

2. Vault Creation Permissions

Starting with version 1.4.0, only users with the admin role can create vaults by default. However, you may configure the create-vaults role to extend this capability to specific users or groups.

To restore the pre-1.4.0 behavior where all users can create vaults:

1. Log in to Keycloak with admin privileges.
2. Navigate to Realm Settings > User Registration > Assign Role.
3. Select and apply the create-vaults role.

This setting grants both new and existing users the create-vaults role.

Recommended Steps for the 1.4.0 Update

We highly recommend updating Keycloak to version 25.0.6. Prior to the update, please verify the following changes:

1. Health Check URL Update
   Modify the Keycloak health check URL as follows:

   - http://localhost:8080/health/live
   + http://localhost:9000/health/live

2. Environment Variable Adjustments
   Update the Keycloak environment variables to the following values:

   - KC_HOSTNAME: keycloak_url
   - KC_PROXY: edge
   + KC_HOSTNAME: https://keycloak_url
   + KC_PROXY_HEADERS: xforwarded

Implementing these changes ensures that Keycloak will start correctly under the new configuration.

1.3.4

What's Changed

• Reworked vault details logic regarding archived vaults and license expiration/seat exceedance #271, #263
• Show License status to the user #264
• Truncate username in member list of vault details #257
• Fixed archived vault migration during Hub upgrade #270
• Fixed frontend shows wrong alert on license expiration/seat exceedance #261

Full Changelog: 1.3.3...1.3.4

1.3.4-beta1

What's Changed

• Reworked vault details logic regarding archived vaults and license expiration/seat exceedance #271, #263
• Show License status to the user #264
• Truncate username in member list of vault details #257
• Fixed archived vault migration during Hub upgrade #270
• Fixed Frontend shows wrong alert on license expiration/seat exceedance #261

Full Changelog: 1.3.3...1.3.4-beta1

1.3.3

What's Changed

Improved handling of Cryptomator Hub licence being exceeded or expired #258

Full Changelog: 1.3.2...1.3.3

1.3.2

What's Changed

• Added new API for legacy device migration #252
• Added headers to instruct the browser how to cache #255
• Removed native queries #254
• Allow Access to /app/admin/settings before finishing onboarding #253

Full Changelog: 1.3.1...1.3.2

1.3.1

What's Fixed

• Fixed compatibility with mobile apps (#224, #250)
• Re-enabled TS linter on CI (#244)

---

Full Changelog: 1.3.0...1.3.1

1.3.0

What's Changed

Important

This release contains major changes. Please read the blog post for this release first to prepare yourself for the update: https://cryptomator.org/blog/2023/12/01/hub-1.3.0/

What's New

• Introduced "Account Key", a new user key pair, for improved access management (#207)
  • Replaced vault admin password with an "owner" role (#211)
  • Streamlined onboarding process (#223)
  • Introduced options to Reset User Account (#228, #240)
• Redesigned screens for unlock success and errors (#236, #245)
• Implemented user identification by key fingerprint during permission grants (#235)
• Synchronized Cryptomator Hub CLI client user with Hub (#239)
• Implemented API changes for Cryptomator Hub CLI (#242, #243)
• Scheduled daily refresh of Hub license (#246)

Other Changes

• Ensured compatibility with nullable vault description in backend (#241)
• Enhanced endpoint documentation, kudos to @chenkins (#201, #204)

---

Full Changelog: 1.2.2...1.3.0

1.3.0 Beta 1

What's Changed

What's New

• Refactor access management by introducing a user key pair #207
• Replace vault admin password with a "owner" role #211
• Refactore Onboarding #223
• View users with their key fingerprint while granting permission #235
• Reset User Account #228 and #240
• Show navigation bar on UnlockSuccess screen #236
• Sync Cryptomator Hub CLI client user to Hub #239
• API changes for Cryptomator Hub CLI #243 and #242

Other Changes

• Honour vault description is nullable in backend #241
• Add some missing endpoint documentation by @chenkins in #201 and #204

---

Full Changelog: 1.2.2...1.3.0-beta1

1.2.2

What's Fixed

Fix Quarkus CVE-2023-4853 (6aaff59)

---

Full Changelog: 1.2.1...1.2.2

1.2.1

What's Fixed

• Frontend not loading after upgrade due to browser cache #220
• Close dropdown in navigation bar after clicking on item 0ef5079

---

Full Changelog: 1.2.0...1.2.1