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
There is no way for users to prevent creation_hooks from running without editing every AccessPolicy to remove them #2116
Comments
bmbouter
added a commit
to bmbouter/pulpcore
that referenced
this issue
Feb 2, 2022
This change adds the `handle_creation_hooks` interface to the ``AccessPolicyFromDB`` method. If the AccessPolicy configured does not have that interface, new model instances created will not have permissions automatically added to them. closes pulp#2116
bmbouter
added a commit
to bmbouter/pulpcore
that referenced
this issue
Feb 2, 2022
This change adds the `handle_creation_hooks` interface to the ``AccessPolicyFromDB`` method. If the AccessPolicy configured does not have that interface, new model instances created will not have permissions automatically added to them. closes pulp#2116
bmbouter
added a commit
to bmbouter/pulpcore
that referenced
this issue
Feb 7, 2022
This change adds the `handle_creation_hooks` interface to the ``AccessPolicyFromDB`` method. If the AccessPolicy configured does not have that interface, new model instances created will not have permissions automatically added to them. closes pulp#2116
bmbouter
added a commit
to bmbouter/pulpcore
that referenced
this issue
Feb 7, 2022
This change adds the `handle_creation_hooks` interface to the ``AccessPolicyFromDB`` method. If the AccessPolicy configured does not have that interface, new model instances created will not have permissions automatically added to them. closes pulp#2116
bmbouter
added a commit
to bmbouter/pulpcore
that referenced
this issue
Feb 7, 2022
This change adds the `handle_creation_hooks` interface to the ``AccessPolicyFromDB`` method. If the AccessPolicy configured does not have that interface, new model instances created will not have permissions automatically added to them. closes pulp#2116
bmbouter
added a commit
to bmbouter/pulpcore
that referenced
this issue
Feb 7, 2022
This change adds the `handle_creation_hooks` interface to the ``AccessPolicyFromDB`` method. If the AccessPolicy configured does not have that interface, new model instances created will not have permissions automatically added to them. closes pulp#2116
bmbouter
added a commit
to bmbouter/pulpcore
that referenced
this issue
Feb 7, 2022
This change adds the `handle_creation_hooks` interface to the ``AccessPolicyFromDB`` method. If the AccessPolicy configured does not have that interface, new model instances created will not have permissions automatically added to them. closes pulp#2116
bmbouter
added a commit
to bmbouter/pulpcore
that referenced
this issue
Feb 8, 2022
This change adds the `handle_creation_hooks` interface to the ``AccessPolicyFromDB`` method. If the AccessPolicy configured does not have that interface, new model instances created will not have permissions automatically added to them. closes pulp#2116
bmbouter
added a commit
to bmbouter/pulpcore
that referenced
this issue
Feb 8, 2022
This change adds the `handle_creation_hooks` interface to the `AccessPolicyFromDB` method. If the AccessPolicy configured does not have that interface, new model instances created will not have permissions automatically added to them. closes pulp#2116
bmbouter
added a commit
to bmbouter/pulpcore
that referenced
this issue
Feb 8, 2022
This change adds the `handle_creation_hooks` interface to the `AccessPolicyFromDB` method. If the AccessPolicy configured does not have that interface, new model instances created will not have permissions automatically added to them. closes pulp#2116
bmbouter
added a commit
to bmbouter/pulpcore
that referenced
this issue
Feb 9, 2022
This change adds the `handle_creation_hooks` interface to the `AccessPolicyFromDB` method. If the AccessPolicy configured does not have that interface, new model instances created will not have permissions automatically added to them. closes pulp#2116
bmbouter
added a commit
to bmbouter/pulpcore
that referenced
this issue
Feb 9, 2022
This change adds the `handle_creation_hooks` interface to the `AccessPolicyFromDB` method. If the AccessPolicy configured does not have that interface, new model instances created will not have permissions automatically added to them. closes pulp#2116
bmbouter
added a commit
to bmbouter/pulpcore
that referenced
this issue
Feb 9, 2022
This change adds the `handle_creation_hooks` interface to the `AccessPolicyFromDB` method. If the AccessPolicy configured does not have that interface, new model instances created will not have permissions automatically added to them. closes pulp#2116
bmbouter
added a commit
to bmbouter/pulpcore
that referenced
this issue
Feb 9, 2022
This change adds the `handle_creation_hooks` interface to the `AccessPolicyFromDB` method. If the AccessPolicy configured does not have that interface, new model instances created will not have permissions automatically added to them. closes pulp#2116
bmbouter
added a commit
to bmbouter/pulpcore
that referenced
this issue
Feb 9, 2022
This change adds the `handle_creation_hooks` interface to the `AccessPolicyFromDB` method. If the AccessPolicy configured does not have that interface, new model instances created will not have permissions automatically added to them. closes pulp#2116
bmbouter
added a commit
that referenced
this issue
Feb 9, 2022
This change adds the `handle_creation_hooks` interface to the `AccessPolicyFromDB` method. If the AccessPolicy configured does not have that interface, new model instances created will not have permissions automatically added to them. closes #2116
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Users want to fully disable the default Authorization of pulp by modifying the DEFAULT_PERMISSION_CLASSES, but even if they do the creation hooks will still be running, likely assigned unwanted permissions to various users and groups.
Solution
Have the calling of creation_hooks happen in side an interface on
AccessPolicyFromDB
, e.g. namedhandle_creation_hooks
or some reasonable name. By delegating the running of creation hooks onto that object, when the user changes it, they won't run anymore.The text was updated successfully, but these errors were encountered: