Task #2360
closed
Create a plan for user authorization in 3.y
0%
Description
This task is successful when reasonable answers to the below questions have been agreed on, and tasks have been created that cover at least the next steps, if not all of the work required.
Q: do we need to introduce a more detailed framework like Django Guardian? (https://github.com/lukaszb/django-guardian )
Q: Will we need to add custom authz logic? What's the scope?
Q: To what extent can/should we migrate existing authz data? Perhaps we should just not.
+1 to not doing this now, but we look at porting the data after we have the new one implemented. In other words, we could green-field use django's auth and decide later.
Also check discussion in the related issue.
Related issues
Updated by ttereshc about 8 years ago
- Related to Task #2090: Create a plan for user/auth in 3.0 added
Updated by bmbouter about 8 years ago
- Subject changed from Create a plan for user authorization in 3.0 to Create a plan for user authorization in 3.y
Since authorization is not part of the MVP I'm retitling it to introduce this in 3.1+
Updated by ttereshc about 8 years ago
Initial thoughts related to authz https://etherpad.net/p/pulp3_authorization_draft
Updated by ttereshc about 8 years ago
- Related to Story #227: [RFE] Allow wildcards in permissions added
Updated by bmbouter over 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
Updated by bmbouter over 5 years ago
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
.