From: "Khetan, Sharad" <sharad.khetan@intel.com>
To: 'susan jasinski' <susantjasinski@gmail.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: RE: OpenBMC GUI navigation -- User vs Security
Date: Mon, 1 Apr 2019 16:45:42 +0000 [thread overview]
Message-ID: <865C376D1B77624AAA570EFEF73CE52F94537DF0@fmsmsx118.amr.corp.intel.com> (raw)
In-Reply-To: <CANT4NrKDC92KOmUcsdP6hWarJKuRP7VTZSwD-F32g+Loqe4VEA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
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.
Ok, I like “Access Control”. Do you agree?
I agree. I would add that “Access Control” is a generic term (as opposed to “User Management”). This means some other items may potentially fall into this category.
On Fri, Mar 29, 2019 at 2:35 PM Ed Tanous <ed.tanous@intel.com<mailto:ed.tanous@intel.com>> wrote:
>
> On 3/28/19 10:06 PM, Khetan, Sharad wrote:
> > 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
>
> +1 "User management" is a very different concept than "Security" and I
> would advocate using a different term on the top level menu.
[-- Attachment #2: Type: text/html, Size: 3413 bytes --]
next prev parent reply other threads:[~2019-04-01 16:45 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
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 [this message]
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=865C376D1B77624AAA570EFEF73CE52F94537DF0@fmsmsx118.amr.corp.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.