Skip to content

💡 [REQUEST] - Refine key-pair management between authority and workspace #185

@john-cremit

Description

@john-cremit

Is there an existing issue for this?

  • I have searched the existing issues

Reference Issues

No response

Problem

No response

Describe the solution you'd like

Currently, the Authority manages a one-to-many relationship with multiple workspaces, where each Authority can be mapped to various workspaces. When creating Access Conditions or configuring secret keys, attributes must follow a format like attr=val@<Authority>-<workspace>#<version>.

Although this format isn't strictly required to ensure functionality — attr=val@<Authority>#<version> technically works — the explicit inclusion of the workspace name enhances manageability.

To improve this, workspace administrators should be able to define and manage the namespaces (key-pairs) used by the Authority. By allowing multiple key-pairs per workspace under a single Authority, we can form a more flexible N:M relationship. This change would increase scalability and provide better organizational clarity.

To-be: attr=val@<workspace_namespace>

Additional context

No response

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions