Google Git Google Git
Sign in
gbmc/gbmcweb/bc68f3bcb1a10a757483d5211e4e228d6a2dee33
commit
bc68f3bcb1a10a757483d5211e4e228d6a2dee33
[log]
author
gBMC Team <gbmc-core@google.com>
Wed Oct 07 16:28:10 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Wed Oct 07 16:29:40 2026 -0700
tree
82831dcf13e8e02d4c672af9c9235722ac9909d4
parent
dd43e5d7c889a502c8ea48dc3a070d578d16d3e1 [diff] 
gbmcweb: Read BootCount directly from D-Bus in getBootNumber

`getBootNumber()` previously used `dbus_utils::getProperty<uint32_t>`, which routes through `ManagedObjectStore` with a 10s–20s polling refresh interval and does not subscribe to `PropertiesChanged` signals for cached `kManagedProperty` entries. As a result, `ManagedObjectStore` can serve a stale `BootCount` or a cached D-Bus error (if queried while `smbios-mdrv2` is restarting) for up to 20 seconds after a host reset.

Query `BootCount` directly via `PostDbusCallToIoContextThreadSafe` so `/redfish/v1/Systems/<str>/Oem/Google/BootNumber` always reflects the live D-Bus property value.

Google-Bug-Id:549301973
PiperOrigin-RevId: 995429600
Change-Id: I5432317334d6b8416416be541d03c0f8fea26a69
3 files changed
tree: 82831dcf13e8e02d4c672af9c9235722ac9909d4
  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. exception_stack_tracer.dynlist
  35. gcovr.cfg
  36. HEADERS.md
  37. LICENSE
  38. meson.build
  39. meson_options.txt
  40. OEM_SCHEMAS.md
  41. OWNERS
  42. PLUGINS.md
  43. README.md
  44. README_GOOGLE.md
  45. Redfish.md
  46. run-ci
  47. setup.cfg
  48. TESTING.md
  49. 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.