Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / bmcweb / 566329ee0f19fed19cca49aafe7a43799f6c0bba
commit566329ee0f19fed19cca49aafe7a43799f6c0bba[log] [tgz]
authorManojkiran Eda <manojkiran.eda@gmail.com>Fri May 22 12:36:17 2020 +0530
committerManojKiran Eda <manojkiran.eda@gmail.com>Wed Jun 17 04:23:15 2020 +0000
tree18ef3519b50a6f08ff88d0db6f47c6ecb6f026b2
parent08bdcc71e5804db9b5c35361e8456e636d258b04 [diff]
Lock Management : Add Support for Mutltiple HMC's

- The Lock Structure already had the HMC-ID field which
  stores the corresponding unique Identifier that tells
  us which HMC has acquired the Lock.

- Now, that the Know you client functionality is up, we can
  leverage the clientId field in the bmcweb session store to
  fill the lock structure with the corresponding hmc identifier.

NOTE : Also note that a Single HMC can have mutliple session that
can acquire different locks, So when the ownership of any lock is
tied up to its cliendId as well as the SessionId.

- Release Lock call on any Transaction ID can only be successful if
  the transactionID of corresponding lock has the complete owner-ship
  as per the NOTE mentioned above.

Tested By:

1. CREATE Session with Client ID as mentioned below:

'{"UserName":"root", "Password":"0penBmc", "Oem":{"OpenBMC" : {"ClientID":<unique id>}}}'

2. Make sure the GetLockList of the above session populates the CliendID field
   as per data mentioned in the login Request.

3. Release Lock on transaction ID with same HMC-ID but with different
   sessionID's should be successful only when both the HMC-ID(mapped to
   X-Auth tokens in the session store) & Session ID(from the session store)
   of the ReleaseLock request matches with the ownwership of the lock pertaining
   to the transaction ID in the request.

Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I60161bea6007782a397fc60f19d44c2211d4cf7f
1 file changed
tree: 18ef3519b50a6f08ff88d0db6f47c6ecb6f026b2
  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.