Drop legacy device support
- Dominant language
- Java
- Stars
- 80
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
### Please agree to the following
- [x] I have searched [existing issues](https://github.com/cryptomator/hub/issues?q=) for duplicates
- [x] I agree to follow this project's [Code of Conduct](https://github.com/cryptomator/hub/blob/develop/.github/CODE_OF_CONDUCT.md)
### Summary
Remove legacy devices with all legacy endpoints, entities, etc. From this point on, only User Key-based devices are supported.
### Motivation
With Hub 1.3.0 we have moved Hub from a device key centric solution to a user key solution. Newly created devices use the user key technique, legacy devices still in use with new clients are migrated to the user key technique, but until now we still allowed legacy devices to unlock vaults. This will change in this issue where we will drop support for legacy devices and remove them from the system.
### Considered Alternatives
_No response_
### Anything else?
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.