All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Khetan, Sharad" <sharad.khetan@intel.com>
To: susan jasinski <susantjasinski@gmail.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: OpenBMC GUI navigation -- User vs Security
Date: Fri, 29 Mar 2019 05:06:08 +0000	[thread overview]
Message-ID: <592E3848-A5D7-45DA-8E20-A3315BE359D9@intel.com> (raw)
In-Reply-To: <CANT4NrJdiFyJBR9SA-jVA0JZ8C=cf7HvBXjxaiHHBEocxaWR6Q@mail.gmail.com>

Hi Susan, 
Typically in server management the notion of security is different than user management. Perhaps “Authentication” or “Access Control” or “Access Management” can be a category for the items you list. 
Thanks,
-Sharad 

> On Mar 28, 2019, at 7:32 PM, susan jasinski <susantjasinski@gmail.com> wrote:
> 
> Currently, the OpenBMC GUI has a single sign-on and there is a menu
> called Users from which that panel is accessed.
> 
> Users
> - Manage User Account
> 
> Now that we are developing LDAP user management and local user
> management, I was thinking we could put them together under a menu
> called "Security" that would replace the "Users" menu.
> 
> Security
> - LDAP User Management
> - Local User Management
> - SSL Certificate Management (including certificate generation)
> - others?
> 
> Does anyone have an option about this?
> 
> Thanks in advance, Susan Jasinski

  reply	other threads:[~2019-03-29  5:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29  2:31 OpenBMC GUI navigation -- User vs Security susan jasinski
2019-03-29  5:06 ` Khetan, Sharad [this message]
2019-03-29 18:48   ` susan jasinski
2019-03-29 19:34   ` Ed Tanous
2019-04-01 16:25     ` susan jasinski
2019-04-01 16:45       ` Khetan, Sharad
2019-05-10  3:11         ` Derick
2019-05-23  2:57           ` OpenBMC GUI Navigation Update Derick
2019-05-23 18:21             ` Gunnar Mills
2019-06-13 20:27               ` Jandra A

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=592E3848-A5D7-45DA-8E20-A3315BE359D9@intel.com \
    --to=sharad.khetan@intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=susantjasinski@gmail.com \
    /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.