Closed phil1995 closed 5 months ago
The changes involve updating the authentication process in the CryptomatorHubAuthenticator. The success case of the retrieveMasterkeyResponse
now includes a header along with the key. Additionally, the success return type has been expanded to include not just the encryptedVaultKey
but also the header
information, which consists of HTTP response headers.
File Path | Change Summary |
---|---|
.../CryptomatorCommonCore/Hub/CryptomatorHubAuthenticator.swift |
Added a header to the success case in retrieveMasterkeyResponse and updated the success return type to include header information. |
In the vault of code where secrets hide, 🐇💻
A rabbit tweaked the lock inside. 🔐
With headers now in success's keep,
Secure the keys that secrets seep. 🗝️✨
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
During the implementation of #332 we somehow forgot to actually pass the header, which includes the Cryptomator Hub subscription state since Hub 1.3.1, to the
HubAuthenticationFlow
after a successful unlock of the Cryptomator Hub vault. This has now been fixed 🎉Summary by CodeRabbit