Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / bmcweb / c6f4e01779afb7a6eb25be15003829b46f81ba4c
commitc6f4e01779afb7a6eb25be15003829b46f81ba4c[log] [tgz]
authorAgata Olender <agata.olender@intel.com>Wed Mar 11 15:19:07 2020 +0100
committerAgata Olender <agata.olender@intel.com>Tue Mar 31 07:43:47 2020 +0000
treea1f7e6a3d4dde75b8d4d1c940cd54cb1d1f480c6
parent988fb7b26942a8ddbaa6be4ce34aa4efe4044b43 [diff]
Add handling of additional parameters of Insert Media action.

Add handling for new parameters:
* Inserted - indicates if virtual media is inserted in the
  virtual device, current implementation supports only True value,
* TransferMethod - the transfer method to use with the image,
  current implementation supports only Stream method,
* transferProtocolType - the network protocol to use with the
  image, current implementation supports CIFS and HTTPS. Protocol
  type should be consistent with image URI prefix.

Make writeProtected param optional.

Tested manually from parameters validation perspective:
- valid values for new params,
- invalid values for new params,
- presence of optional params.

Change-Id: I135cb5ac181a442578d70821468214d0a8bcf0f6
Signed-off-by: Agata Olender <agata.olender@intel.com>
1 file changed
tree: a1f7e6a3d4dde75b8d4d1c940cd54cb1d1f480c6
  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. config.h.in
  17. DEVELOPING.md
  18. JenkinsFile
  19. LICENCE
  20. MAINTAINERS
  21. pam-webserver
  22. README.md
  23. 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 secp384r1 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.