All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derick <derick.montague@gmail.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: "Khetan, Sharad" <sharad.khetan@intel.com>
Subject: Re: OpenBMC GUI navigation -- User vs Security
Date: Thu, 9 May 2019 22:11:49 -0500	[thread overview]
Message-ID: <CAOUmYFTYtxQBJk7iRAVJ7YUgH2-z_t=i9R1opwifJ72M97XaFA@mail.gmail.com> (raw)
In-Reply-To: <865C376D1B77624AAA570EFEF73CE52F94537DF0@fmsmsx118.amr.corp.intel.com>

> 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.

This is the last email I could find on this thread. I would like to
verify we have reached consensus as we are approaching the time to
update the navigational structure from "Users" to "Access Control".
Once the "LDAP Settings" and "Certificate Management" work is
completed, we will be ready for the change.

Current Navigation Structure
- Users
  - Manage User Account

Proposed Navigation Structure
- Access Control
  - Certificate Management
  - LDAP User Management
  - Local User Management

  reply	other threads:[~2019-05-10  3:12 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
2019-05-10  3:11         ` Derick [this message]
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='CAOUmYFTYtxQBJk7iRAVJ7YUgH2-z_t=i9R1opwifJ72M97XaFA@mail.gmail.com' \
    --to=derick.montague@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=sharad.khetan@intel.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.