Project

General

Profile

Bug #160

need resource restriction capability

Added by Matt Jones about 19 years ago. Updated over 17 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Owen Eddins
Category:
SRB MCAT
Target version:
Start date:
10/14/2000
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
160

Description

Earlier versions of the SRB allowed any user to access and write to any
SRB-registered storage resource. We need to be able to specify restrictions on
the use of resources such that a particular site manager can indicate which
users can write to the resource. This might be accomplished through a
user/group ACl mechanism, or through srb domain capabilities, or otherwise.

History

#1 Updated by Matt Jones about 19 years ago

Check with Raja (Arcto Rajasekar). He has told us in the past that this feature
was at least partially completed.

#2 Updated by Matt Jones over 18 years ago

Lowered priority because SRB no longer in immediate plans for deployment.

#3 Updated by Matt Jones over 18 years ago

Deferred indefinitely because SRB deployment is in question. Will reopen later
if we decide to deploy the SRB.

#4 Updated by Matt Jones over 17 years ago

Consolidating products to those we actually are maintaining.

#5 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 160

Also available in: Atom PDF