Project

General

Profile

Story #1475

Need system for users to request access to resources

Added by Matthew Jones about 13 years ago. Updated over 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Authentication, Authorization
Target version:
-
Start date:
2011-05-31
Due date:
% Done:

0%

Story Points:
Sprint:

Subtasks

Task #1596: Document use case for user requesting access to some resourceRejectedDave Vieglais

History

#1 Updated by Matthew Jones about 13 years ago

  • Assignee set to Matthew Jones
  • Category set to Authentication, Authorization

Users that are denied access to a resource currently have no recourse. Need a system that provides the following features:

1) Allow users to request access (read, write, ownership) to a resource
2) Resource owners are notified of request
3) Resource owners have a UI for granting or denying this access (ideally, via a web UI linked from the notfication), with explanation
4) Requesting user is notified of decision

#2 Updated by Dave Vieglais almost 13 years ago

  • Position set to 1
  • Position deleted (41)
  • Target version set to Sprint-2011.23-Block.3

#3 Updated by Dave Vieglais almost 13 years ago

  • Position set to 14
  • Position deleted (24)
  • Target version changed from Sprint-2011.23-Block.3 to Sprint-2011.26-Block.4

#4 Updated by Dave Vieglais over 12 years ago

  • Position deleted (39)
  • Target version deleted (Sprint-2011.26-Block.4)
  • Position set to 1

#5 Updated by Dave Vieglais over 12 years ago

  • Position set to 13
  • Position deleted (22)

#6 Updated by Dave Vieglais over 12 years ago

  • Position set to 5
  • Position deleted (112)

#7 Updated by Dave Vieglais over 9 years ago

  • Start date deleted (2011-05-31)

#8 Updated by Bruce Wilson over 9 years ago

  • Milestone set to None

A use case here is where someone has been given the ID for a dataset (perhaps in an R script), but lacks permission to access the data. A possible resolution (from a UI perspective) is to provide the user with a query that returns the (readable) resource maps that contain that object, which would potentially lead the user to the science metadata (if that's readable as well). DataONE does return a Forbidden result where the user has access, acknowledging that the object exists (as opposed to always returning not found). Acknowledging existence is a desired behavior and should not change. If the user has no authorization to the resource map or the science metadata, then there is no recourse.

BEW: My opinion is that if the user has no read access to the data object or the resource map that contains it, that case needs to be a "won't fix". The user needs to work through the chain by which they got the reference. It may be possible to create a process that allows the user to request that the authoritative member node be notified of a request for access. This needs to be something that the user initiates, but that's also hard to handle from an automated process perspective.

#9 Updated by Dave Vieglais over 6 years ago

  • Status changed from New to Rejected

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)