commit | 29e2bdd7b4418dc7d6c48ca701eb2a3832aab090 | [log] [tgz] |
---|---|---|
author | Chinmay Shripad Hegde <hosmanechinmay@gmail.com> | Fri Jun 06 16:23:47 2025 +0530 |
committer | Ed Tanous <ed@tanous.net> | Mon Jun 23 23:19:32 2025 +0000 |
tree | cd7b7581775b0339bfdae79ddbd9a356e4f574e8 | |
parent | be1384e3add6a57e1908443e28f49247403a947b [diff] |
Task: Fix missing properties in task monitor Task monitor URI when the task is running contains partial information. Properties like progress percent, message is missing. Same issue is present when task is created and response is returned. This patch fixes missing properties in task creation response and task monitor URI. Tested: - Task creation with fwupdate response shows all properties - Task monitor URI provides complete information when running - Verified task creation and monitor response for log service Change-Id: I77c6d9b9302d13b8480cf5a3419b8c6754e5049d Signed-off-by: Chinmay Shripad Hegde <hosmanechinmay@gmail.com> Signed-off-by: Ed Tanous <etanous@nvidia.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.