An admin connot see his organisation's packages #25538
Labels
Comments
|
An additional problem is that the user who owns the package can no longer publish (it denies access with a 403), but other users who are members of the project can. |
|
I have the same issue. I cannot access my own packages and get 404 errors in the UI and unauthorization errors in my docker pipelines when being a owner. |
|
This may be fixed by #25707. |
silverwind
pushed a commit
that referenced
this issue
Jul 9, 2023
Fixes (?) #25538 Fixes https://codeberg.org/forgejo/forgejo/issues/972 Regression #23879 #23879 introduced a change which prevents read access to packages if a user is not a member of an organization. That PR also contained a change which disallows package access if the team unit is configured with "no access" for packages. I don't think this change makes sense (at the moment). It may be relevant for private orgs. But for public or limited orgs that's useless because an unauthorized user would have more access rights than the team member. This PR restores the old behaviour "If a user has read access for an owner, they can read packages". --------- Co-authored-by: Giteabot <teabot@gitea.io>
GiteaBot
added a commit
to GiteaBot/gitea
that referenced
this issue
Jul 9, 2023
Fixes (?) go-gitea#25538 Fixes https://codeberg.org/forgejo/forgejo/issues/972 Regression go-gitea#23879 go-gitea#23879 introduced a change which prevents read access to packages if a user is not a member of an organization. That PR also contained a change which disallows package access if the team unit is configured with "no access" for packages. I don't think this change makes sense (at the moment). It may be relevant for private orgs. But for public or limited orgs that's useless because an unauthorized user would have more access rights than the team member. This PR restores the old behaviour "If a user has read access for an owner, they can read packages". --------- Co-authored-by: Giteabot <teabot@gitea.io>
silverwind
pushed a commit
that referenced
this issue
Jul 9, 2023
Backport #25707 by @KN4CK3R Fixes (?) #25538 Fixes https://codeberg.org/forgejo/forgejo/issues/972 Regression #23879 #23879 introduced a change which prevents read access to packages if a user is not a member of an organization. That PR also contained a change which disallows package access if the team unit is configured with "no access" for packages. I don't think this change makes sense (at the moment). It may be relevant for private orgs. But for public or limited orgs that's useless because an unauthorized user would have more access rights than the team member. This PR restores the old behaviour "If a user has read access for an owner, they can read packages". Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
lunny
added
the
issue/critical
lunny
removed
the
issue/critical
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
I do the update to the rc 1.20.0
Une utilisateur dont le nom d'utilisateur est "IO-Projects" n'a plus access au package de sont organisation. Cela étant dit le package est public, et si aucun utilisateur n'est connecté celui-ci reste accessible comme voulu.
Gitea Version
1.20.0+rc
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
under my user :
under the owner user :
without being connected :
Git Version
No response
Operating System
No response
How are you running Gitea?
on docker
Database
MySQL
The text was updated successfully, but these errors were encountered: