Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / bmcweb / 9fbf8532d22f7d976c29fc62827fccc515ea31a6
commit9fbf8532d22f7d976c29fc62827fccc515ea31a6[log] [tgz]
authorrajeeranjan <ranjan.rajeev1609@gmail.com>Wed Jul 23 23:25:52 2025 +0530
committerEd Tanous <ed@tanous.net>Mon Nov 03 15:29:37 2025 +0000
tree1138c51d3e7c00964bad0bc1ee1521d5cfbbc253
parentb0ae71c8f503b9e56a5bf88549346b15e7961e26 [diff]
Allow multipart update when no targets are specified

If no targets are provided, bmcweb will automatically select the sole
software object that implements both the StartUpdate and
xyz.openbmc_project.Software.MultipartUpdate interfaces [1], provided
there is only one such object; otherwise, the behavior remains unchanged
(an error requiring explicit target is returned).

This enables support for PLDM [2], which uses a single StartUpdate API
and handles multi-component updates internally [3]. If multiple
MultipartUpdate instances are present and no targets are specified,
an error is returned.

Behavior:
- Single target specified: Unchanged; updates proceed as before.
- No targets specified: If exactly one entity implements both
MultipartUpdate interface and StartUpdate, invoke StartUpdate on it.
Otherwise, return an error requiring explicit target.
- Multiple targets: Not supported, return an error (unchanged).

[1] https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/78905
[2] https://gerrit.openbmc.org/c/openbmc/pldm/+/79192
[3] https://gerrit.openbmc.org/c/openbmc/docs/+/76645

Tests:
- FW Update using Multipart URI
```
curl -X POST -k https://{ip}/redfish/v1/UpdateService/update-multipart --form 'UpdateParameters={"Targets":[]};type=application/json' --form "UpdateFile=@vbios.fwpkg;type=application/octet-stream"
{
  "@odata.id": "/redfish/v1/TaskService/Tasks/0",
  "@odata.type": "#Task.v1_4_3.Task"
  ...
  "PercentComplete": 0,
  "StartTime": "2025-08-05T13:33:23+00:00",
  "TaskMonitor": "/redfish/v1/TaskService/TaskMonitors/0",
  "TaskState": "Running",
  "TaskStatus": "OK"
}
```

Signed-off-by: Rajeev Ranjan <ranjan.rajeev1609@gmail.com>
Change-Id: I294b1447b6faf2055419d3659f9c963aeb6d5d0d
1 file changed
tree: 1138c51d3e7c00964bad0bc1ee1521d5cfbbc253
  1. .github/
  2. config/
  3. docs/
  4. features/
  5. http/
  6. include/
  7. redfish-core/
  8. scripts/
  9. src/
  10. static/
  11. subprojects/
  12. test/
  13. .clang-format
  14. .clang-tidy
  15. .codespell-ignore
  16. .dockerignore
  17. .eslintignore
  18. .gitignore
  19. .markdownlint.yaml
  20. .openbmc-enforce-gitlint
  21. .prettierignore
  22. .shellcheck
  23. DEVELOPING.md
  24. LICENSE
  25. meson.build
  26. meson.options
  27. OWNERS
  28. README.md
  29. run-ci
README.md

OpenBMC webserver

This component attempts to be a "do everything" embedded webserver for OpenBMC.

Features

The webserver implements a few distinct interfaces:

  • DBus event websocket. Allows registering on changes to specific dbus paths, properties, and will send an event from the websocket if those filters match.
  • OpenBMC DBus REST api. Allows direct, low interference, high fidelity access to dbus and the objects it represents.
  • Serial: A serial websocket for interacting with the host serial console through websockets.
  • Redfish: A protocol compliant, DBus to Redfish translator.
  • KVM: A websocket based implementation of the RFB (VNC) frame buffer protocol intended to mate to webui-vue to provide a complete KVM implementation.

Protocols

bmcweb at a protocol level supports http and https. TLS is supported through OpenSSL. Http1 and http2 are supported using ALPN registration for TLS connections and h2c upgrade header for http connections.

AuthX

Authentication

Bmcweb supports multiple authentication protocols:

  • Basic authentication per RFC7617
  • Cookie based authentication for authenticating against webui-vue
  • Mutual TLS authentication based on OpenSSL
  • Session authentication through webui-vue
  • XToken based authentication conformant to Redfish DSP0266

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.

Authorization

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.

Configuration

bmcweb is configured per the meson build files. Available options are documented in meson_options.txt

Compile bmcweb with default options

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.

Use of persistent data

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.

TLS certificate generation

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.

Compression

bmcweb supports various forms of http compression, including zstd and gzip. Client headers are observed to determine whether compressed payloads are supported.

Redfish Aggregation

bmcweb is capable of aggregating resources from satellite BMCs. Refer to AGGREGATION.md for more information on how to enable and use this feature.