Google GitGoogle Git
Sign in
gbmc/gbmcweb/9a2d89b55c144b878618e0f0b2d12db8b429540b
commit
9a2d89b55c144b878618e0f0b2d12db8b429540b
[log]
author
gBMC Team <gbmc-core@google.com>
Wed Aug 19 16:39:08 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Wed Aug 19 16:40:25 2026 -0700
tree
3def225eee8f98b73a50aa2b39e8a38349f9284b
parent
930c5196e9f8f8a9e81f43b24368c4ca61cd4320 [diff]
Validate chassis path before populating FanZone Chassis link

Update asyncPopulatePid to verify that the chassis name extracted from the PID zone configuration path exists in the inventory. Instead of unconditionally setting the Chassis link, the code now queries the inventory subtree paths and only populates the Chassis link if a matching chassis is found. Unit tests have been added to verify behavior for both valid and invalid chassis configurations.

Google-Bug-Id:545645561
PiperOrigin-RevId: 967474295
Change-Id: I9af3608887d53435f2509879ed6510ed0974917c
2 files changed
tree: 3def225eee8f98b73a50aa2b39e8a38349f9284b
  1. .github/
  2. config/
  3. devpath_plugin/
  4. g3/
  5. http/
  6. include/
  7. install/
  8. plugins/
  9. redfish-core/
  10. redfish_authorization/
  11. scripts/
  12. src/
  13. static/
  14. subprojects/
  15. test/
  16. tlbmc/
  17. .clang-format
  18. .clang-tidy
  19. .clang-tidy-ignore
  20. .dockerignore
  21. .gitignore
  22. .markdownlint.yaml
  23. .openbmc-enforce-gitlint
  24. .openbmc-no-clang
  25. .openbmc-no-sanitize
  26. .prettierignore
  27. .shellcheck
  28. AGGREGATION.md
  29. CLIENTS.md
  30. COMMON_ERRORS.md
  31. copy.bara.sky
  32. DBUS_USAGE.md
  33. DEVELOPING.md
  34. gcovr.cfg
  35. HEADERS.md
  36. LICENSE
  37. meson.build
  38. meson_options.txt
  39. OEM_SCHEMAS.md
  40. OWNERS
  41. PLUGINS.md
  42. README.md
  43. README_GOOGLE.md
  44. Redfish.md
  45. run-ci
  46. setup.cfg
  47. TESTING.md
  48. UNIT_TESTING.md
README.md

OpenBMC webserver

This project is Google's version of BMCWeb.

See Readme Google for Google added features. The following is the original README of OpenBMC/BMCWeb.

==============================================================================

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.

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

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.