commit | a87c4180fd7f2127960fbc4c89c31b7659f0cfb8 | [log] [tgz] |
---|---|---|
author | vijayabharathi shetty <vijayabharathix.shetty@intel.com> | Tue May 16 12:26:56 2023 +0000 |
committer | vijayabharathi shetty <vijayabharathix.shetty@intel.com> | Tue May 16 12:26:56 2023 +0000 |
tree | c9d1d1df8d987ea1a6b3f032bb79d39b35f711cc | |
parent | b7790deeba910ccf956ca1cfe91049fce547dae6 [diff] |
Fix certificate replacement error code issue We get 500 Internal Server Error when we try to replace certificate without providing certificate but expected response is 400 Bad Request. So fixed the issue by removal of overriding the error code. Tested: Response for attempt to replace certificate without certificate or without required json key Before changes: 500 Internal Server Error After changes: 400 Bad Request Change-Id: I7f672d40f73f8cd1491625ba6714bd3ad2594faf Signed-off-by: vijayabharathi shetty <vijayabharathix.shetty@intel.com>
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 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
.
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.
bmcweb is capable of aggregating resources from satellite BMCs. Refer to AGGREGATION.md for more information on how to enable and use this feature.