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

Only register top-level namespaces while we bootstrap authorization for sub-spacing #333

Closed
jhiemstrawisc opened this issue Nov 6, 2023 · 1 comment · Fixed by #460
Closed
Assignees
Labels
bug Something isn't working
Milestone

Comments

@jhiemstrawisc
Copy link
Member

Right now, nothing prevents me from registering /jhiemstra as a namespace and someone else from registering /jhiemstra/foo as a namespace. Eventually we should make sure this kind of sub-spacing is authorized by the entity that owns /jhiemstra.

For now, while we bootstrap up to that kind of authorization, we should at least enforce that if /jhiemstra is already registered, /jhiemstra/foo is restricted. Likewise, if /jhiemstra/foo is already registered, we should restrict registration of the parent space /jhiemstra.

@jhiemstrawisc jhiemstrawisc added this to the v7.3.0 milestone Nov 6, 2023
@jhiemstrawisc jhiemstrawisc self-assigned this Nov 6, 2023
@bbockelm bbockelm added the bug Something isn't working label Nov 7, 2023
@jhiemstrawisc
Copy link
Member Author

Closed by PR #460

@haoming29 haoming29 linked a pull request Dec 6, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants