Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / bmcweb / 3a58c5a8f5f753a3229f6af85ebf3e85f1a44387
commit3a58c5a8f5f753a3229f6af85ebf3e85f1a44387[log] [tgz]
authorKonstantin Aladyshev <aladyshev22@gmail.com>Mon Aug 05 12:57:13 2024 +0300
committerEd Tanous <ed@tanous.net>Tue Sep 03 23:47:49 2024 +0000
tree9e9db85957d646f480e1a4a098d4678b1c15be35
parent478b7adffab38c98d880ad2c39c8dc421433bd92 [diff]
Require Inventory.Item.PCIeDevice for PCIe objects

Currently when bmcweb tries to get PCIe device service it checks only
path and doesn't limit search by any required interface.
This can lead to wrong result if the 'xyz.openbmc_project.ObjectMapper'
for example have object with the same path.
To fix the issue require xyz.openbmc_project.Inventory.Item.PCIeDevice
interface to be present in the object.

Tested:
Patchest was tested on the system with a DBUS service that has objects
with the "xyz.openbmc_project.Inventory.Item.PCIeDevice" interface.

Before the change request to the PCIe device endpoint like
/redfish/v1/Systems/system/PCIeDevices/Bus_00_Device_00
outputs internal error message.

After the change request to the PCIe device endpoint like
/redfish/v1/Systems/system/PCIeDevices/Bus_00_Device_00
outputs detailed PCIe device info including all the relevant links
to its PCIe functions.

Change-Id: I25d60533fa8f7bdda26c81bde1fa0a88c25365f6
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
1 file changed
tree: 9e9db85957d646f480e1a4a098d4678b1c15be35
  1. .github/
  2. config/
  3. http/
  4. include/
  5. redfish-core/
  6. scripts/
  7. src/
  8. static/
  9. subprojects/
  10. test/
  11. .clang-format
  12. .clang-tidy
  13. .codespell-ignore
  14. .dockerignore
  15. .eslintignore
  16. .gitignore
  17. .markdownlint.yaml
  18. .openbmc-enforce-gitlint
  19. .prettierignore
  20. .shellcheck
  21. AGGREGATION.md
  22. CLIENTS.md
  23. COMMON_ERRORS.md
  24. DBUS_USAGE.md
  25. DEVELOPING.md
  26. HEADERS.md
  27. LICENSE
  28. meson.build
  29. meson.options
  30. OEM_SCHEMAS.md
  31. OWNERS
  32. README.md
  33. Redfish.md
  34. REDFISH_CHECKLIST.md
  35. run-ci
  36. TESTING.md
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.

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.

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.