Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / bmcweb / 53d9a6668f7d20c46aea33d5163a143ccf35e643
commit53d9a6668f7d20c46aea33d5163a143ccf35e643[log] [tgz]
authorRichard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com>Mon Sep 30 11:52:08 2019 +0530
committerRichard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com>Tue Oct 29 01:00:48 2019 +0000
tree6737b4167846c838c78329e33e132574a8b54c02
parent9e27a22edc4434ec577c2eb4034edc6874088413 [diff]
bmcweb: Message entry for Manufacturing mode

Message entry added for manufacturing mode entry and exit,
which is part of special mode property as defined in
xyz/openbmc_project/Control/Security/SpecialMode.interface.yaml.
These message entries are used to indicate whenever
SpecialMode state of the BMC is updated from normal value
and manufacturing mode and vice versa

Tested:
1. Redfish validator - passed for this new addition
2. Log will be as below
{
    "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
    "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/317",
    "@odata.type": "#LogEntry.v1_4_0.LogEntry",
    "Created": "1970-01-01T00:05:17+00:00",
    "EntryType": "Event",
    "Id": "317",
    "Message": "Entered Manufacturing Mode.",
    "MessageArgs": [],
    "MessageId": "OpenBMC.0.1.ManufacturingModeEntered",
    "Name": "System Event Log Entry",
    "Severity": "Critical"
},
{
    "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
    "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/899",
    "@odata.type": "#LogEntry.v1_4_0.LogEntry",
    "Created": "1970-01-01T00:14:59+00:00",
    "EntryType": "Event",
    "Id": "899",
    "Message": "Exited Manufacturing Mode.",
    "MessageArgs": [],
    "MessageId": "OpenBMC.0.1.ManufacturingModeExited",
    "Name": "System Event Log Entry",
    "Severity": "OK"
}

Change-Id: I182eeedb6860a3abcd4054caa431150ed073fbad
Signed-off-by: Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com>
1 file changed
tree: 6737b4167846c838c78329e33e132574a8b54c02
  1. cmake/
  2. http/
  3. include/
  4. redfish-core/
  5. scripts/
  6. src/
  7. static/
  8. .clang-format
  9. .gitignore
  10. bmcweb.service.in
  11. bmcweb.socket
  12. build_x86.sh
  13. cmake-format.json
  14. CMakeLists.txt
  15. CMakeLists.txt.in
  16. DEVELOPING.md
  17. JenkinsFile
  18. LICENCE
  19. MAINTAINERS
  20. pam-webserver
  21. README.md
  22. Redfish.md
README.md

OpenBMC webserver

This component attempts to be a "do everything" embedded webserver for openbmc.

Capabilities

At this time, the webserver implements a few interfaces:

  • Authentication middleware that supports cookie and token based authentication, as well as CSRF prevention backed by linux PAM authentication credentials.
  • An (incomplete) attempt at replicating phosphor-dbus-rest interfaces in C++. Right now, a few of the endpoint definitions work as expected, but there is still a lot of work to be done. The portions of the interface that are functional are designed to work correctly for phosphor-webui, but may not yet be complete.
  • Replication of the rest-dbus backend interfaces to allow bmc debug to logged in users.
  • An initial attempt at a read-only redfish interface. Currently the redfish interface targets ServiceRoot, SessionService, AccountService, Roles, and ManagersService. Some functionality here has been shimmed to make development possible. For example, there exists only a single user role.
  • SSL key generation at runtime. See the configuration section for details.
  • Static file hosting. Currently, static files are hosted from the fixed location at /usr/share/www. This is intended to allow loose coupling with yocto projects, and allow overriding static files at build time.
  • Dbus-monitor over websocket. A generic endpoint that allows UIs to open a websocket and register for notification of events to avoid polling in single page applications. (this interface may be modified in the future due to security concerns.

Configuration

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

  • is issued by C=US, O=OpenBMC, CN=testhost,
  • is valid for 10 years,
  • has a random serial number, and
  • is signed using the SHA-256 algorithm.