Providing encryption key secret - not working?

Hello

The documentation says that the key length should be a string with 32 character. If I “decompile” the auto generated key then that one is much larger.

So can you confirm that 32 ASCII alpha-numeric characters are ok ?

Thanks
John

1 Like

Hello @jamoser,
Can you please link the documentation on this?

1 Like

1 Like

Seems providing the encryption key does not work

encryptionKey →

{“t”:{“$date”:“2022-11-02T16:13:05.695+00:00”},“s”:“E”, “c”:“STORAGE”, “id”:29038, “ctx”:“initandlisten”,“msg”:“Exception in EncryptionKeyDB::init: {e}”,“attr”:{“e”:“cannot read stats of encryption key file: /etc/mongodb-encryption/encryption-key: No such file or directory”}}

encryption-key →

{“t”:{“$date”:“2022-11-02T16:15:15.252+00:00”},“s”:“E”, “c”:“STORAGE”, “id”:29038, “ctx”:“initandlisten”,“msg”:“Exception in EncryptionKeyDB::init: {e}”,“attr”:{“e”:“Invalid base64 character”}}

so what is the correct procedure to create a encryption key and set it as a secret ?

1 Like

Not sure why I have answer my questions myself in this forum …

→ the encryption key has to be base64 encoded twice !!!

1 Like

Hello @jamoser,
This forum is for the community and is community-driven. It is not a free alternative to paid support. Other users and Percona employees volunteer their free time to assist the community. If you require faster answers, please reach out percona.com/support to engage in a support contract.

Glad you discovered the issue. If you can, please help us improve the clarity of the documentation by submitting a pull request.

1 Like

May be I am in the wrong movie … so you guys are producing bugs and we can be lucky, that we can experience the bugs and help to fix them ?

Do we need to have a call with your manager ?

1 Like

@jamoser,
We are not producing bugs, no. This is clearly a simple documentation mistake. If you’d like to help out the rest of the community, it would be appreciated.

1 Like