-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
getUploadToken: ERR_CRYPTO_INVALID_STATE #50
Comments
@samsoncsyu7777 : Have you define the secret value in secret manager API? How is the parameter configured inside config.ts under folder /functions/src/ for following parameters:
|
Thank you for your help.
[image: image.png]
We have secret key in secret manager.
Here is the encryption part in config.ts:
encryption: {
defaultAlgorithm: "aes-256-cbc",
keyPath: "EncryptionKey",
defaultVersion: 1,
},
…On Sun, 10 May 2020 at 00:53, ALEXIS SINGLAIRE ***@***.***> wrote:
@samsoncsyu7777 <https://github.com/samsoncsyu7777> : Have you define the
secret value in secret manager API?
How is the parameter configured inside config.ts under folder
/functions/src/ for following parameters:
- defaultAlgorithm
- keyPath
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#50 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHIDKQLBC3EXRWJEKSKJSEDRQYXNZANCNFSM4M44KQNQ>
.
|
Is your secret key name called 'EncryptionKey'? How you build the secret value? Are you using head command to create the secret value ? Refer to this screenshot for the secret key name |
I followed the instructions (command line) of readme to build it.
…On Sun, May 10, 2020, 8:48 AM ALEXIS SINGLAIRE, ***@***.***> wrote:
Is your secret key name called 'EncryptionKey'? How you build the secret
value? Are you using head command to create the secret value ?
Refer to this screenshot for the secret key name
#51 (comment)
<#51 (comment)>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#50 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHIDKQLG2PHVMMQPJBAA2E3RQ2PCRANCNFSM4M44KQNQ>
.
|
Is it good to delete the secret key and build it again?
On Sun, May 10, 2020, 8:53 AM Samson Samson, <[email protected]>
wrote:
… I followed the instructions (command line) of readme to build it.
On Sun, May 10, 2020, 8:48 AM ALEXIS SINGLAIRE, ***@***.***>
wrote:
> Is your secret key name called 'EncryptionKey'? How you build the secret
> value? Are you using head command to create the secret value ?
>
> Refer to this screenshot for the secret key name
>
> #51 (comment)
> <#51 (comment)>
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#50 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AHIDKQLG2PHVMMQPJBAA2E3RQ2PCRANCNFSM4M44KQNQ>
> .
>
|
Hi, can you give screenshot of your secret key name similar to sample.of screenshot I gave you? If you use head command to create the secret value, then you need to define defaultAlgorithm value as aes-256-gcm. |
It works. Thank you very much. |
When a user enters PIN to upload, there is an error logged in Firebase functions getUploadToken: Unhandled error Error [ERR_CRYPTO_INVALID_STATE]: Invalid state for operation getAuthTag. What can I do to fix it?
The text was updated successfully, but these errors were encountered: