commit | b31cef67c03c77d55db8a507a240eb87fa455bf7 | [log] [tgz] |
---|---|---|
author | Ed Tanous <edtanous@google.com> | Thu Jun 30 17:51:46 2022 -0700 |
committer | Ed Tanous <ed@tanous.net> | Tue Aug 16 18:58:10 2022 +0000 |
tree | 20c37adf5a627cbd09e05ad9875480626c708b3f | |
parent | 7be4c8adf0e831c5a5465afebcb4e7c364963da7 [diff] |
task payload, initialize jsonValue in constructor We should do this because it means that variables are only initialized once. In the simplest case: struct MyClass{ std::string myString MyClass(){ myString = "foo"; } } in the language, myString is constructed twice, once with empty string, then a second time with "foo". If you do the construction in the initializer list for the class the construction only happens once. Now, the above case is contrived, the optimizer can see through it and likely optimizes this case because std::string is relatively simple, but for more complex structures, it's possible this generates less and bettercompiled code, and this is worth having the check for, and making our existing code correct. Tested: cppcheck passing. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: Ie5c7f293598408d437e7bf7b3fc93b0819e25f9f
This component attempts to be a "do everything" embedded webserver for OpenBMC.
The webserver implements a few distinct interfaces:
bmcweb at a protocol level supports http and https. TLS is supported through OpenSSL.
Bmcweb supports multiple authentication protocols:
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.
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.
bmcweb is configured per the meson build files. Available options are documented in meson_options.txt
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
.
bmcweb by default is compiled with runtime logging disabled, as a performance consideration. To enable it in a standalone build, add the
-Dlogging='enabled'
option to your configure flags. If building within Yocto, add the following to your local.conf.
EXTRA_OEMESON:pn-bmcweb:append = "-Dbmcweb-logging='enabled'"
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.
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.