Bug #3024

[API] Synchronize read permissions and collection name links

Added by Tom Clegg over 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
1.0

Description

See #3036, which will make this story irrelevant.

Currently, it is possible to have a collection in a project (i.e., a name link has tail=project head=collection) with no corresponding permission link. This means a user can be in the position of having can_read permission on the project (therefore see a link to a collection in Workbench) but not having can_read permission on the collection itself (therefore the link yields 404).


Related issues

Related to Arvados - Story #3036: [API] Use regular uuids instead of content hashes to identify collectionsResolved08/07/2014

History

#1 Updated by Tom Clegg over 7 years ago

  • Target version set to Arvados Future Sprints

#2 Updated by Tom Clegg over 7 years ago

  • Description updated (diff)

#3 Updated by Tom Clegg over 7 years ago

  • Subject changed from Synchronize read permissions and collection name links to [API] Synchronize read permissions and collection name links

#4 Updated by Tom Clegg over 7 years ago

  • Target version changed from Arvados Future Sprints to Deferred

#5 Updated by Tom Clegg about 7 years ago

  • Status changed from New to Resolved

#6 Updated by Ward Vandewege about 7 years ago

  • Target version deleted (Deferred)

Also available in: Atom PDF