Skip to content
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

FEATURE: Setting for encryptionKey #3425

Open
1 task done
christophlehmann opened this issue Dec 21, 2024 · 0 comments
Open
1 task done

FEATURE: Setting for encryptionKey #3425

christophlehmann opened this issue Dec 21, 2024 · 0 comments
Labels

Comments

@christophlehmann
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Description

The encryption key is normally a persistent filesystem cache entry. Currently it can't get overwritten with a setting. In environments that should not have local persistent data it would be handy to define it manually.

Possible Solution

No response

christophlehmann pushed a commit to christophlehmann/flow-development-collection that referenced this issue Dec 21, 2024
With this the encryption key can be defined in a setting.
When defined it is not received from cache anymore.

Resolves: neos#3425
christophlehmann pushed a commit to christophlehmann/flow-development-collection that referenced this issue Dec 21, 2024
With this the encryption key can be defined in a setting.
When defined it is not received from cache anymore.

Resolves: neos#3425
christophlehmann pushed a commit to christophlehmann/flow-development-collection that referenced this issue Dec 22, 2024
With this the encryption key can be defined in a setting.
When defined it is not received from cache anymore.

Resolves: neos#3425
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant