Bug: 403 when opening library dashboard as "guillermotest" team member

[gviedma-aulasneo]

Current behavior
Opening the library dashboard URL for a library where the user "guillermo test" is a team member returns a 403.

Expected behavior
User can access the dashboard and see the Team Members list if the have "view team member" permission over thar library.

Steps to reproduce

1. Log in as the team member account “guillermotest” (pass: jajaSalu2)
2. Open:
   https://apps.singapore.edunext.cloud/admin-console/authz/libraries/lib:OpenedX:CSPROB
3. Observe the 403 response.

Comments
This may be tied to missing Studio access. Access to this route should depend only on the “view team members” permission, not on Studio access. It is important to note that if you had the "Author" or "Admin" role in the previous version, you automatically gained access to the studio and library, and that behavior should remain unchanged.

[MaferMazu]

@gviedma-aulasneo I assigned myself to this issue. I removed the release blocker tag because the code cut happened.
I would like to wait a bit to have the final changes in stage and try to reproduce this behavior to see if it is a bug or something we already fixed. Thanks for your patience.

[mariajgrimaldi]

I'll be trying to reproduce this with our latest changes :) I'll report back here

[mariajgrimaldi]

@gviedma-aulasneo, could you share a bit more detail?

1. How did you assign yourself library team perms?
2. I manually checked the roles for the library lib:OpenedX:CSPROB and got the following:

{
  "count": 4,
  "next": null,
  "previous": null,
  "results": [
    {
      "role": "library_admin",
      "permissions": [
        "view_library",
        "manage_library_tags",
        "delete_library",
        "edit_library_content",
        "publish_library_content",
        "reuse_library_content",
        "view_library_team",
        "manage_library_team",
        "create_library_collection",
        "edit_library_collection",
        "delete_library_collection"
      ],
      "user_count": 0
    },
    {
      "role": "library_author",
      "permissions": [
        "view_library",
        "manage_library_tags",
        "edit_library_content",
        "publish_library_content",
        "reuse_library_content",
        "view_library_team",
        "create_library_collection",
        "edit_library_collection",
        "delete_library_collection"
      ],
      "user_count": 0
    },
    {
      "role": "library_contributor",
      "permissions": [
        "view_library",
        "manage_library_tags",
        "edit_library_content",
        "reuse_library_content",
        "view_library_team",
        "create_library_collection",
        "edit_library_collection",
        "delete_library_collection"
      ],
      "user_count": 0
    },
    {
      "role": "library_user",
      "permissions": [
        "view_library",
        "reuse_library_content",
        "view_library_team"
      ],
      "user_count": 0
    }
  ]
}

3. I'm not sure which previous behavior you mean. I'm testing on a plain Teak install and seeing the same results as in our sandbox. Could you describe what you're seeing so I can try to reproduce it on my end?

[gviedma-aulasneo]

1. I did it with one of the test users who holds manage_library_team
2. Have you tried to grant that user a role as a team member? I tried to grant and revoke the role a few times, but it was harder to keep the state as the list had a bug that didn't update correctly at the time.
3. If a user register and somebody add them to a library team, they gain access to the library and Studio. I use this sandbox https://apps.sandbox.openedx.edly.io/ to test the behavior. Glad to help reproduce the bug in a synchronous session