Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / bmcweb / ff0a08815ee289a7a67c31e9bb460cb240daad67
commitff0a08815ee289a7a67c31e9bb460cb240daad67[log] [tgz]
authorJayaprakash Mutyala <mutyalax.jayaprakash@intel.com>Wed Jun 26 09:08:53 2024 +0000
committerJayaprakash Mutyala <mutyalax.jayaprakash@intel.com>Wed Jun 26 09:08:53 2024 +0000
treea7abff04fb3252aa36280a1a9b86385a86dbe7e8
parent9c95be77a6ef219ec4bf72c88a8ceab77478d0ed [diff]
Fix Redfish Event monitor issue in listener

Issue: Listener not receiving the events generated. SubmitTestEvent
directly writes a test event to the HttpClient and listener sees it.
But, in the case of services generated events, redfish event logs are
written to /var/log/redfish. iNotify is used to determine if any new
Redfish event log is generated.

Below patch causing this issue not to notify the redfish event log to
listener.
https://gerrit.openbmc.org/c/openbmc/bmcweb/+/70915

Fix: Code changes made to get iNotify properly so that listener receives
the events generated by server once subscription is successful.

Tested:
- Once subscription generated successfully. Tested client receiving
 events successfully by running command on BMC console

Signed-off-by: poram srinivasa rao <poramx.srinivasa.rao@intel.com>
Signed-off-by: Jayaprakash Mutyala <mutyalax.jayaprakash@intel.com>
Change-Id: Id6ff5236eb57ba861210696e41caa838ab78034e
1 file changed
tree: a7abff04fb3252aa36280a1a9b86385a86dbe7e8
  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. .gitignore
  16. .markdownlint.yaml
  17. .openbmc-enforce-gitlint
  18. .prettierignore
  19. .shellcheck
  20. AGGREGATION.md
  21. CLIENTS.md
  22. COMMON_ERRORS.md
  23. DBUS_USAGE.md
  24. DEVELOPING.md
  25. HEADERS.md
  26. LICENSE
  27. meson.build
  28. meson_options.txt
  29. OEM_SCHEMAS.md
  30. OWNERS
  31. README.md
  32. Redfish.md
  33. REDFISH_CHECKLIST.md
  34. run-ci
  35. 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.