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

Adding RBAC (Role Based Access Control) support to pulp_deb #392

Closed
pulpbot opened this issue Jan 4, 2022 · 7 comments
Closed

Adding RBAC (Role Based Access Control) support to pulp_deb #392

pulpbot opened this issue Jan 4, 2022 · 7 comments

Comments

@pulpbot
Copy link
Member

pulpbot commented Jan 4, 2022

Author: @quba42 (quba42)

Redmine Issue: 7315, https://pulp.plan.io/issues/7315


pulpcore 3.6 adds experimental RBAC support. This may be declared safe to use with pulpcore 3.7.

Plugins can start taking advantage of this feature at their own choosing.

Plugin writers doc:

https://github.com/pulp/pulpcore/tree/master/docs/plugins/plugin-writer/concepts/rbac

@pulpbot pulpbot added this to the Wishlist milestone Jan 4, 2022
@quba42 quba42 removed New labels Jan 31, 2022
@stale
Copy link

stale bot commented May 25, 2022

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

@stale stale bot added the stale label May 25, 2022
@cleonn
Copy link

cleonn commented Jun 7, 2023

At Linkoping University we are using pulp2 and are currently working on migrating to pulp3. This is a must have for us to fully decommission pulp2! Can we have it? :) We really need feature parity with pulp_rpm with regard to rbac. (There will probably be Swedish Candy for the fixer!)

@stale
Copy link

stale bot commented Jun 7, 2023

This issue is no longer marked for closure.

@stale stale bot removed the stale label Jun 7, 2023
@quba42
Copy link
Collaborator

quba42 commented Jun 7, 2023

@cleonn We currently have no plans/capacity to work on RBAC. I also don't have a clear conception what this entails. Given you seem to have some conception of "RBAC feature parity with pulp_rpm", would you (or anyone from your team) be willing to write something like a specification document for what is needed?

This would help get a conversation about RBAC in pulp_deb started. The best place to start that conversation is probably an RFC in the community forum: https://discourse.pulpproject.org/c/development/8

@cleonn
Copy link

cleonn commented Jun 7, 2023

@cleonn We currently have no plans/capacity to work on RBAC. I also don't have a clear conception what this entails. Given you seem to have some conception of "RBAC feature parity with pulp_rpm", would you (or anyone from your team) be willing to write something like a specification document for what is needed?

This would help get a conversation about RBAC in pulp_deb started. The best place to start that conversation is probably an RFC in the community forum: https://discourse.pulpproject.org/c/development/8

Thanks! We will finnish configuring and running pulp_rpm first and see exactly what we are missing and get back to this issue in a while!

@mdellweg
Copy link
Member

mdellweg commented Jun 7, 2023

I also don't have a clear conception what this entails.

It is all about writing meaningful (default) access policies on all the viewsets.

The hard part is usually discussing how much lockdown is needed/useful/not-too-inconvenient.

@quba42
Copy link
Collaborator

quba42 commented Aug 23, 2023

I only want to have one open issue for Domains/RBAC/multi tenancy support right now, so I am closing this in favor of #860

@quba42 quba42 closed this as completed Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants