commit | f5e29f33e61be81ece4b2f78d7d1750d357f7ff3 | [log] [tgz] |
---|---|---|
author | JunLin Chen <Jun-Lin.Chen@quantatw.com> | Wed Dec 08 16:47:04 2021 +0800 |
committer | Ed Tanous <ed@tanous.net> | Wed Dec 08 18:31:19 2021 +0000 |
tree | f3852ddd8a82ad669da59e6212ae8b0516e7e962 | |
parent | 1e270c5f5436a856ed2d43fde2288b87aed23998 [diff] |
Fix bmcweb crash problem when no-auth After insecure-disable-auth=enabled. it is not needed to do login and establish session before request. GET /redfish/v1/AccountService/Accounts won't get any status code and cause the bmcweb service crashed. Set the default string value for `thisUser`. Assign the user only if the session is not nullptr. Test: Use no-auth: curl -k -X GET https://<bmcip>/redfish/v1/AccountService/Accounts { "@odata.id": "/redfish/v1/AccountService/Accounts", "@odata.type": "#ManagerAccountCollection.ManagerAccountCollection", "Description": "BMC User Accounts", "Members": [], "Members@odata.count": 0, "Name": "Accounts Collection" } Use basic-auth: curl -k -u root:0penBmc -X GET https://<bmcip>/redfish/v1/AccountService/Accounts { "@odata.id": "/redfish/v1/AccountService/Accounts", "@odata.type": "#ManagerAccountCollection.ManagerAccountCollection", "Description": "BMC User Accounts", "Members": [ { "@odata.id": "/redfish/v1/AccountService/Accounts/root" } ], "Members@odata.count": 1, "Name": "Accounts Collection" } Signed-off-by: JunLin Chen <Jun-Lin.Chen@quantatw.com> Change-Id: Ifa9844c4dbc2f172338b24fba7a09ae013b6d473 Signed-off-by: Willy Tu <wltu@google.com>
This component attempts to be a "do everything" embedded webserver for openbmc.
At this time, the webserver implements a few interfaces:
BMCWeb is configured by setting -D
flags that correspond to options in bmcweb/meson_options.txt
and then compiling. For example, meson <builddir> -Dkvm=disabled ...
followed by ninja
in build directory. The option names become C++ preprocessor symbols that control which code is compiled into the program.
meson builddir ninja -C builddir
meson builddir -Dbuildtype=minsize -Db_lto=true -Dtests=disabled ninja -C buildir
If any of the dependencies are not found on the host system during configuration, meson automatically gets them via its wrap dependencies mentioned in bmcweb/subprojects
.
meson builddir -Dwrap_mode=nofallback ninja -C builddir
meson builddir -Dbuildtype=debug ninja -C builddir
meson builddir -Db_coverage=true -Dtests=enabled ninja coverage -C builddir test
When BMCWeb starts running, it reads persistent configuration data (such as UUID and session data) from a local file. If this is not usable, it generates a new configuration.
When BMCWeb SSL support is enabled and a usable certificate is not found, it will generate a self-sign a certificate before launching the server. The keys are generated by the secp384r1
algorithm. The certificate
C=US, O=OpenBMC, CN=testhost
,SHA-256
algorithm.