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

Permissions Registry and permissions handler #12713

Open
mattiagiupponi opened this issue Nov 11, 2024 · 0 comments
Open

Permissions Registry and permissions handler #12713

mattiagiupponi opened this issue Nov 11, 2024 · 0 comments
Assignees
Milestone

Comments

@mattiagiupponi
Copy link
Contributor

Overview

The permissions in geonode are static, GeoNode itself is the only one who can decide the permissions to be assigned to a resource. This is not always true because my thrid party application may want to override a specific permissions and provide it by default.
Some workflow may not be required to be included by default in GeoNode (like advanced workflow) but just activated if needed

Proposed By

@mattiagiupponi

Assigned to Release

GeoNode 5.x

Proposal

We will create a PermissionsRegistry where GeoNode and other apps can register their own PermissionsHandler which will be responsible to add/change/modify the permissions payload before save it.
The read permissions part will not be changed since it will automatically get the changes applied on the permissiosn

Backwards Compatibility

None

@mattiagiupponi mattiagiupponi added this to the 5.0.0 milestone Nov 11, 2024
@mattiagiupponi mattiagiupponi self-assigned this Nov 11, 2024
@mattiagiupponi mattiagiupponi changed the title Permissions Registry and permissions handler Permissions Registry and permissions handler Nov 11, 2024
mattiagiupponi added a commit that referenced this issue Nov 11, 2024
mattiagiupponi added a commit that referenced this issue Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant