All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Joseph <tomjose@linux.vnet.ibm.com>
To: "Tanous, Ed" <ed.tanous@intel.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Mapping LDAP group to user roles
Date: Thu, 23 Aug 2018 18:50:08 +0530	[thread overview]
Message-ID: <2d7b2647-cc0a-bcaf-c1fa-d6da05769502@linux.vnet.ibm.com> (raw)
In-Reply-To: <7E9441B1E5EFFD4681F54958E821699345832E4D@ORSMSX114.amr.corp.intel.com>



On Tuesday 21 August 2018 08:51 PM, Tanous, Ed wrote:
>> We have a requirement to assign role to the LDAP users, so certain
>> operations can be restricted for users without admin permissions.
>>
> It would be great if you could document your proposal as a patch to the existing user management document here:
> https://github.com/openbmc/docs/blob/master/user_management.md
https://gerrit.openbmc-project.xyz/#/c/openbmc/docs/+/12091/
>
> It would make it much easier to see what changes you're proposing.  Given what already exists, your proposal is a little confusing, as there's already a mechanism to get group membership, and defined the user roles.  Are you proposing changing the existing interfaces to the new group collection type interface?  You're proposing two user roles, but we already have documented 4 user roles.  Is your proposal to delete two of them?
>
> I think all of these questions would be answered if you could update the document above with your proposed changes.
In phosphor-rest-server the requirement is to add two privilege roles, 
the admin and the user role. So the interface has two roles proposed. 
This can be extended in the future to include other privilege roles.

  reply	other threads:[~2018-08-23 13:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 12:13 Mapping LDAP group to user roles Tom Joseph
2018-08-21 15:21 ` Tanous, Ed
2018-08-23 13:20   ` Tom Joseph [this message]
2018-08-23 16:29     ` Tanous, Ed
2018-08-28 14:55       ` Tom Joseph
2018-08-28 15:42         ` Thomaiyar, Richard Marian
2018-08-29 11:51           ` Ratan Gupta
2018-08-29 17:13             ` Thomaiyar, Richard Marian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2d7b2647-cc0a-bcaf-c1fa-d6da05769502@linux.vnet.ibm.com \
    --to=tomjose@linux.vnet.ibm.com \
    --cc=ed.tanous@intel.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.