commit | ce22f6099e7e28ae26591348bf484ebedbc1ed42 | [log] [tgz] |
---|---|---|
author | Paul Fertser <fercerpav@gmail.com> | Mon Jun 03 20:53:16 2024 +0000 |
committer | Paul Fertser <fercerpav@gmail.com> | Tue Jun 04 10:04:18 2024 +0000 |
tree | 0d4be6b10ab1e5d468f80a6ca5f2a5e8c6e3b9dc | |
parent | aa848de216d501c2c6dd00e3599a3d7a86eaa660 [diff] |
Expose current Role in Session object As discussed at https://gerrit.openbmc.org/c/openbmc/webui-vue/+/70758 having that information available to front end is desired for UX purposes (hiding pages and actions that are not permitted to the current user anyway). This field was added in #Session.v1_7_0.Session released on 2023.2. Tested: current role correctly reported (e.g. "Administrator") as the only array element, Redfish-Service-Validator passes. Fixes: #275 Change-Id: Ic9d8f02ca5859cb4b9996fd85b0896ce76ea22aa Signed-off-by: Paul Fertser <fercerpav@gmail.com>
This component attempts to be a "do everything" embedded webserver for OpenBMC.
The webserver implements a few distinct interfaces:
bmcweb at a protocol level supports http and https. TLS is supported through OpenSSL.
Bmcweb supports multiple authentication protocols:
Each of these types of authentication is able to be enabled or disabled both via runtime policy changes (through the relevant Redfish APIs) or via configure time options. All authentication mechanisms supporting username/password are routed to libpam, to allow for customization in authentication implementations.
All authorization in bmcweb is determined at routing time, and per route, and conform to the Redfish PrivilegeRegistry.
*Note: Non-Redfish functions are mapped to the closest equivalent Redfish privilege level.
bmcweb is configured per the meson build files. Available options are documented in meson_options.txt
meson setup builddir ninja -C builddir
If any of the dependencies are not found on the host system during configuration, meson will automatically download them via its wrap dependencies mentioned in bmcweb/subprojects
.
bmcweb relies on some on-system data for storage of persistent data that is internal to the process. Details on the exact data stored and when it is read/written can seen from the persistent_data
namespace.
When SSL support is enabled and a usable certificate is not found, bmcweb will generate a self-signed a certificate before launching the server. Please see the bmcweb source code for details on the parameters this certificate is built with.
bmcweb is capable of aggregating resources from satellite BMCs. Refer to AGGREGATION.md for more information on how to enable and use this feature.