From: Lei Yu <yulei.sh@bytedance.com>
To: openbmc <openbmc@lists.ozlabs.org>
Subject: Potential impact with bmcweb pam config change
Date: Wed, 10 Jan 2024 10:48:46 +0800 [thread overview]
Message-ID: <CAGm54UHeY-gg_otQ_UOTLCqO52cqsooTkvW6VBHpmOWyCPSuxQ@mail.gmail.com> (raw)
This email describes a change in bmcweb's pam config file and the
potential impact of the user login.
# Background
See details at https://gerrit.openbmc.org/c/openbmc/bmcweb/+/68562
In short, the previous bmcweb pam config is incorrect, and a user
without the `web/redfish` group could log in to bmcweb.
# Potential impact
With the change, users without the `redfish` group will **NOT** be
able to login to bmcweb anymore.
If an old BMC is upgraded with this change, and if the previous BMC
users were created without the `redfish` group, such users will be
locked out from bmcweb.
# Questions
The questions to discuss:
1. Are there real cases in which BMC users were created without the
`redfish` group?
2. If yes, how to migrate from the old BMC without any accident
lockout, and still enforce the `redfish` group check?
--
BRs,
Lei YU
reply other threads:[~2024-01-10 2:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAGm54UHeY-gg_otQ_UOTLCqO52cqsooTkvW6VBHpmOWyCPSuxQ@mail.gmail.com \
--to=yulei.sh@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).