Opened 16 years ago

Closed 15 years ago

Last modified 15 years ago

#982 closed defect (duplicate)

Wrong destination (for shared to user) from link to directory from transformation

Reported by: Johan Vallon-Christersson Owned by: Nicklas Nordborg
Priority: major Milestone:
Component: core Version:
Keywords: Cc:

Description

After running a plugin (that creates directories and files and performs a transformation) in an experiment shared to a project (as described in ticket:980) I have manually shared created items to the project. When a colleague of mine (a member of the active project) follows a link in the transformation that point to a directory (my directory but shared to project), he incorrectly ends up in his own home directory.

Change History (12)

comment:1 by Jari Häkkinen, 16 years ago

Milestone: BASE 2.8
Owner: changed from everyone to Johan Vallon-Christersson

Johan check this issue.

in reply to:  1 comment:2 by Johan Vallon-Christersson, 16 years ago

Replying to jari:

Johan check this issue.

Will check after Lund Onk production installation runs 2.8

comment:3 by Johan Vallon-Christersson, 16 years ago

Milestone: BASE 2.8BASE 2.8.1

comment:4 by Jari Häkkinen, 16 years ago

Milestone: BASE 2.8.3BASE 2.x+

in reply to:  3 comment:5 by Johan Vallon-Christersson, 15 years ago

Replying to johan:
Have tested in 2.8.4 without success.

Some new specification on the error and how to recreate the problem available below.


UserA owns ExperimentX. The experiment directory (ExpDir) is owned by UserA and is located under /home/UserA/projects/ExpDir

ExperimentX and ExpDir is shared to ProjectX and UserB is a member of ProjectX.

UserB runs a plugin in experimentX that creates directory PluginDir and some files that are placed in PluginDir.

PluginDir is created in ExpDir (/home/UserA/projects/ExpDir/PluginDir) and owner is set to UserB.

When UserB follows link to PluginDir (/home/UserA/projects/ExpDir/PluginDir) from transformation, he incorrectly ends up in his own home directory (/home/UserB).

comment:6 by Johan Vallon-Christersson, 15 years ago

Owner: changed from Johan Vallon-Christersson to Nicklas Nordborg

comment:7 by Johan Vallon-Christersson, 15 years ago

Milestone: BASE 2.x+BASE 2.9

comment:8 by Nicklas Nordborg, 15 years ago

Are all directories on the path shared to UserB? The directory tree only includes directories that are visible for the logged in user and since it must be a tree there can be no "holes". Eg. the entire path leading to a directory must be visible for the user.

in reply to:  8 comment:9 by Jari Häkkinen, 15 years ago

Replying to nicklas:

Are all directories on the path shared to UserB? The directory tree only includes directories that are visible for the logged in user and since it must be a tree there can be no "holes". Eg. the entire path leading to a directory must be visible for the user.

No. But if UserB gets read permission for all directories down to the result directory then the results become visible. This has a major implication

  • All users in my projects must have read to my home and other directories.

Of course, the other users will only see whatever I decide to share but there will be a lot of read sharing.

I thought the idea was that once the result in the analysis tree was done and a user opted for browsing the resulting files directly from a transformation would end up in the correct directory view regardless permission in other directories. The user must of course have the proper permissions for the directory where the results reside. Is this possible to realize such a use case?

comment:10 by Nicklas Nordborg, 15 years ago

Milestone: BASE 2.9BASE 2.x+

It is a limitation in the web client. It loads directories top-down and will not reach a subdirectory unless a user has read permission for all directories leading to it.

comment:11 by Nicklas Nordborg, 15 years ago

Resolution: duplicate
Status: newclosed

Replaced by #1178.

comment:12 by Jari Häkkinen, 15 years ago

Milestone: BASE 2.x+
Note: See TracTickets for help on using tickets.