Bug #1287

folders created by analyze user are not visible

Added by Mark Donohoe about 1 year ago. Updated 8 months ago.

Status:Closed Start date:02/23/2012
Priority:Normal Due date:
Assignee:Mary Laser % Done:

0%
Category:User Permissions
Target version:-
Rank: Tester:

Description

Using svn 5531 on randos64.ostt, a user was created with analyze permissions (ana2). The user created a folder called ana2. The folder is not visible when browsing, the root folder shows a +, but it won't open. See screen shots. The folder exists in the db.

To reproduce:
1. create user with analyze permissions, folder is Software Repository.
2. login as that user
3. create a folder put it under SR.
4. browse, can you see the folder or have Software Repository expand? (I tried both the + and expand, neither worked).

folderCreated.png - shows folder created OK (82.1 kB) Mark Donohoe, 02/23/2012 10:06 pm

NoAna2Folder.png - shows that the folder is not visible, + nor Expand work (70 kB) Mark Donohoe, 02/23/2012 10:06 pm

History

#1
Updated by Mark Donohoe about 1 year ago

This defect also applies to a user with delete permission. When logged in as fossy, the folder is visible.
If the ana2 account is changed to have the ana2 folder as it's primary folder instead of SR, then when ana2 is logged in the ana2 folder is visible, but when creating a subfolder under the ana2 folder, the same problem occurs, ana2 folder cannot be expanded and the subfolder is not accessible.

#2
Updated by Mark Donohoe about 1 year ago

If an upload is loaded into the subfolder it becomes visible. So it appears that it's only empty subfolders that are not visible/usable. The subfolders do appear in the upload screens even when empty so that's good. To verify that it's empty subfolders another subfolder was created under the ana2 subfolder and it's not visible/usable in browse.

#3
Updated by Mary Laser about 1 year ago

  • Category changed from Permissions to User Permissions
  • Assignee changed from Bob Gobeille to Mary Laser
  • Target version changed from 2.0.0 to 2.0.1

Will defer to after 2.0

#4
Updated by Mary Laser 9 months ago

  • Target version deleted (2.0.1)

#5
Updated by Bob Gobeille 8 months ago

  • Status changed from New to Closed

Rolling up into http://www.fossology.org/issues/2349 since the solution (a permission API) might solve many issues.

Also available in: Atom PDF