Skip to content

Allow for (optional) Redis Key Prefix #52034

Open
@jsmueller7

Description

@jsmueller7

Support Namespacing in Redis
I've been looking into data separation in Redis. Nextcloud supports Redis ACL by allowing a username and password to be set. However, the way Nextcloud uses Redis makes it difficult to implement namespacing in Redis, i.e. to specify in the Redis access control list which user is allowed to access which keys. The Nextcloud keys apparently have the format <user-uuid>/locked/<file-uuid>.

Is your feature request related to a problem? Please describe.
Not that I see.

Describe the solution you'd like
The solution would be for Nextcloud to use (optionally definable) prefixes for its Redis keys, e.g. nextcloud:<uuid>/locked/<uuid>.

Describe alternatives you've considered
Do not support multi-client capability in Redis (which corresponds to the setup in most cases).

Metadata

Metadata

Assignees

No one assigned

    Labels

    0. Needs triagePending check for reproducibility or if it fits our roadmapenhancement

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions