| commit | a78d3e618eb919a62731c54223e7851a912c9450 | [log] [tgz] |
|---|---|---|
| author | Sunitha Harish <sunithaharish04@gmail.com> | Thu Nov 28 23:19:57 2019 -0600 |
| committer | James Feist <james.feist@linux.intel.com> | Fri Dec 06 17:18:04 2019 +0000 |
| tree | 97e88bb77b0dc19d560823c3fbaf2c74580f4203 | |
| parent | d82a3acd1abc04a13f90cef5234416c3e18da0e1 [diff] |
Fix response error code for error - Unauthorized
Tested by:
Request: Creating session with wrong credential.
curl --insecure -X POST -D headers.txt https://${BMC_IP}/redfish/v1/SessionService/Sessions
-d '{"UserName":"root", "Password":"penBmc"}'
Resonse Error code: HTTP/1.1 401 Unauthorized
Signed-off-by: Sunitha Harish <sunithaharish04@gmail.com>
Change-Id: I9c7b0af644f1e3d987b4f76e4206bbb276aba035
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/CMakeLists.txt and then compiling. For example, cmake -DBMCWEB_ENABLE_KVM=NO ... followed by make. The option names become C++ preprocessor symbols that control which code is compiled into the program.
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 prime256v1 algorithm. The certificate
C=US, O=OpenBMC, CN=testhost,SHA-256 algorithm.