Skip to content

404 Repo Inaccessible for Users in Team w/ All Repo Access #17003

Closed
@SoulSeekkor

Description

@SoulSeekkor
  • Gitea version (or commit ref): 1.15.2 built with GNU Make 4.1, go1.16.7 : bindata, sqlite, sqlite_unlock_notify
  • Git version: 2.33.0.2
  • Operating system: Windows Server 2012 R2
    Running using your pre-built Win x64 binary. This is being started/stopped using a Windows service created per your installation instructions running as a local user with 'full control' of relevant folders.
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No (Couldn't register or email was taking a super long time to come. May have to try this later.)

Description

  1. Create new organization as admin user and make it private.
  2. Create a new empty repo named 'test'.
  3. Create new team named 'read-only' with all repo access, read, with everything toggled OFF except code.
  4. Add a regular (and restricted) test user to the read-only team.
  5. Attempt for that user to access the repo they should have access to will fail with a 404.

Note that creating the team and THEN creating the repo works fine, just not in reverse. The retroactively applied permissions for a team created after the repo was created is botched.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions