Project

General

Profile

Actions
Copy link

Feature #10826

closed

MDSAuthCaps should have gids field as well as uid field

Added by John Spray about 9 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
Labels (FS):
Pull request ID:

Description

(As sage pointed out last week)

Currently we have a place to put a UID limit (i.e. only allow client to act as this UID), but we should also allow a list of GIDs here to fully express what a given user would be permitted to access.

And then at some point actually enforce this stuff...

Actions
Copy link
 #1

Updated by Greg Farnum about 9 years ago

This may need to be more complicated and allow a list of UIDs as well — depending on deployment scenarios, it's easy to imagine colocated users sharing a single Ceph client mount that needs to act for each of them.

Actions
Copy link
 #2

Updated by John Spray almost 8 years ago

  • Status changed from New to Resolved
commit 1d82ec469e266f4a49893b974224efe5233c3101
Author: Sage Weil <sage@redhat.com>
Date:   Thu May 28 00:33:07 2015 -0400

    mds/MDSAuthCaps: parse optional gid list

    Signed-off-by: Sage Weil <sage@redhat.com>
Actions
Copy link

Also available in: Atom PDF