fix: incorrect encryption string instructions #15086
Open
+2
−2
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.
What does this PR do?
As outlined in #13290, any new calcom user following the .env example is unable to perform any administrative function as 2FA is required.
Because
"latin1"
is specified as the encryption/decryption method inlib/crypto.ts
, using a base64 encoded string (as is currently suggested) results in a 44 length string, which breaks the 2FA process.A cleaner solution would be to update
crypto.ts
directly, but this was already rejected in #13484 in favour of the ongoing refactor in #12698. This PR is a temporary fix until the larger refactor has been completed.Mandatory Tasks