Skip to content

Document permissions needed for listing deb releases, release components, etc. #1266

New issue
New issue
Open
Open
Document permissions needed for listing deb releases, release components, etc.#1266
Labels
.docCHANGES/<issue_number>.docLooking_for_ContributorFor valid issues that the plugin maintainers have no plans to implement.Triage-Needed

Description

@grzleadams
grzleadams
opened on Apr 23, 2025

We're trying to use a non-admin user to list and create deb repository releases, release components, packages, and package release components, but keep getting 403s even after giving the account deb.apt{repository,distribution}_owner on the needed objects. I don't see any roles (we're on 3.73) that even reference those things. What permissions are actually needed to list and/or create those?

Activity

  1. grzleadams
    added
    Triage-Needed
    on Apr 23, 2025
  2. quba42
    added
    Looking_for_ContributorFor valid issues that the plugin maintainers have no plans to implement.
    .docCHANGES/<issue_number>.doc
    on Apr 24, 2025

  3. grzleadams commented on Apr 24, 2025

    @grzleadams
    grzleadams
    on Apr 24, 2025
    Author

    An example of the 403s:

    DEBUG:urllib3.connectionpool:[https://pulp.domain:443](https://pulp.domain/) "GET /pulp/api/v3/content/deb/release_architectures/?distribution=focal&architecture=x86_64 HTTP/1.1" 403 63
ERROR:root:{'detail': 'You do not have permission to perform this action.'}
ERROR:root:Error: 403 Forbidden
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    .docCHANGES/<issue_number>.docLooking_for_ContributorFor valid issues that the plugin maintainers have no plans to implement.Triage-Needed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions