Emergency Access #390
Draft
Emergency Access #390
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* `vault.requiredEmergencyKeyShares` * `vault.emergencyKeyShares`
…ION process and fill GROUPS with memberSize
…yaccess/UserListGroupVisualization
# Conflicts: # backend/src/main/java/org/cryptomator/hub/api/UsersResource.java # backend/src/main/java/org/cryptomator/hub/api/VaultResource.java # backend/src/main/java/org/cryptomator/hub/entities/User.java # backend/src/main/java/org/cryptomator/hub/entities/VaultAccess.java # backend/src/main/java/org/cryptomator/hub/filters/VaultRole.java # frontend/src/common/backend.ts # frontend/src/components/NavigationBar.vue # frontend/src/router/index.ts
# Conflicts: # backend/src/main/java/org/cryptomator/hub/api/AuditLogResource.java # backend/src/test/java/org/cryptomator/hub/api/VaultResourceIT.java # backend/src/test/resources/org/cryptomator/hub/flyway/V9999__Test_Data.sql
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces comprehensive support for emergency access and recovery features in the backend API, including new endpoints, event logging, and configuration options. The changes span multiple files to add new resource classes, extend DTOs, update audit logging, and enhance settings management.
Emergency Access and Recovery Features
EmergencyAccessResourceREST API, which enables users to start, approve, complete, abort, and delete emergency recovery processes, as well as manage recovered key shares. This includes new DTOs for recovery processes and key shares.Settings and Configuration
SettingsResourceandSettingsDtoto allow configuration of emergency access options, such as enabling/disabling emergency access, council member IDs, required key shares, minimum members, and council selection. Also added audit logging for emergency access settings changes.User Account Management
UsersResourceto remove emergency key shares and recovery process key shares for the user, ensuring proper cleanup during account reset.General Improvements
AuthorityDtoand its subclasses with@JsonInclude(JsonInclude.Include.NON_NULL)to avoid serializing null fields in API responses.These changes collectively provide robust emergency access and recovery capabilities, improve auditability, and enhance configuration flexibility.