| /openbmc/bmcweb/docs/ |
| H A D | TESTING.md | 10 There are a variety of ways to develop and test bmcweb software changes. Here
20 - Clone bmcweb from gerrit
23 git clone ssh://openbmc.gerrit/openbmc/bmcweb/
27 [README.md](https://github.com/openbmc/bmcweb#configuration) to compile
32 arm-openbmc-linux-gnueabi-strip bmcweb
39 - Copy your bmcweb daemon you want to test to /tmp/ in QEMU
42 scp -P 2222 bmcweb root@127.0.0.1:/tmp/
49 - Stop bmcweb service within your QEMU session
52 systemctl stop bmcweb
55 **Note:** bmcweb daemon supports being started directly in parallel with the
[all …]
|
| H A D | HEADERS.md | 1 # bmcweb headers
3 **Why does bmcweb use so many headers? My build times are slow!**
7 bmcweb at one point was a crow-based project. Evidence of this can still be seen
11 headers. As bmcweb evolved, it needed more capabilities, so the core was ported
24 <https://gerrit.openbmc.org/c/openbmc/bmcweb/+/49039>
36 <https://gerrit.openbmc.org/c/openbmc/bmcweb/+/37445> Doing this exposed a
46 - Reduce the bmcweb binary size to the point where link time optimization is not
47 required for most usages. About half of the bmcweb build time is spent doing
48 link time optimization, which, as of this time is required to keep bmcweb code
|
| H A D | CLIENTS.md | 3 bmcweb being a user and network facing daemon, is subject to a vast array of
5 non-exhaustive list of tests and clients that bmcweb is expected to be
7 category are intended to be qualification tests to ensure the bmcweb meets the
11 The base expectation is that for master versions of bmcweb, and master versions
13 limitations in the testing tools behavior within bmcweb to make the tools pass,
18 Redfish-Service-Validator: A tool to verify through GET requests that bmcweb
40 testssl.sh: A tool for verifying the correctness of the bmcweb cipher suites
|
| H A D | COMMON_ERRORS.md | 1 # Commonly recurring errors in bmcweb
3 What follows is a list of common errors that new users to bmcweb tend to make
5 developing in bmcweb, the maintainers highly recommend reading and understanding
122 bmcweb uses a single reactor for all operations. Blocking that reactor for any
146 nature of bmcweb, they are not required to be explicitly threadsafe, but they
173 async bmcweb code. While capturing by reference can be useful, given how
174 difficult these types of bugs are to triage, bmcweb explicitly requires that all
183 BMCWEB("/foo/bar");
187 where the behavior must differ) all URL handlers should end in "/". The bmcweb
203 Very commonly, bmcweb maintainers and contributors alike have to do audits of
[all …]
|
| /openbmc/bmcweb/ |
| H A D | README.md | 21 bmcweb at a protocol level supports http and https. TLS is supported through
29 Bmcweb supports multiple authentication protocols:
44 All authorization in bmcweb is determined at routing time, and per route, and
52 bmcweb is configured per the
56 ## Compile bmcweb with default options
65 mentioned in `bmcweb/subprojects`.
69 bmcweb relies on some on-system data for storage of persistent data that is
75 When SSL support is enabled and a usable certificate is not found, bmcweb will
77 bmcweb source code for details on the parameters this certificate is built with.
81 bmcweb supports various forms of http compression, including zstd and gzip.
[all …]
|
| H A D | OWNERS | 1 # Below lists the current bmcweb maintainers. bmcweb is used in a number of
5 # - Have a solid understanding of the bmcweb core code, and how it's used.
10 # It is expected that bmcweb maintainers participate on a majority of code
19 # how it interacts with OpenBMC, and how the bmcweb implementation compares to
25 # for resources implemented within the Redfish standard. bmcweb maintainers
32 # harnesses that bmcweb needs to pass, listed in CLIENTS.md, and at least a
36 # APIs that bmcweb uses, and their limitations in versioning, consistency, and
39 # - Join and answer questions of the #bmcweb-and-redfish channel within
43 # bmcweb.
49 # bmcweb is the primary attacker/client facing application on the network, it
[all …]
|
| H A D | DEVELOPING.md | 132 bmcweb's Redfish implementation, including Redfish OEM Resources, shall conform
133 to the Redfish specification. Please keep bmcweb's
134 [Redfish support document](https://github.com/openbmc/bmcweb/blob/master/docs/Redfish.md)
136 [OEM SCHEMAS](https://github.com/openbmc/bmcweb/blob/master/docs/OEM_SCHEMAS.md).
143 [Common Errors](https://github.com/openbmc/bmcweb/blob/master/docs/COMMON_ERRORS.md).
153 - Why are the changes useful? Given that bmcweb is a user-facing daemon, commits
175 To that end, bmcweb will do its' best to insulate clients from breaking api
180 configurable would increase the software complexity, therefore bmcweb makes
188 Special note: Code exists in bmcweb that is missing upstream backends to make it
204 .clang-tidy file in the root of bmcweb, and are expected to be passing.
[all …]
|
| /openbmc/bmcweb/test/http/ |
| H A D | router_test.cpp | 17 // IWYU pragma: no_forward_declare bmcweb::AsyncResp
30 [](const Request&, const std::shared_ptr<bmcweb::AsyncResp>&) {}; in TEST()
65 [](const Request&, const std::shared_ptr<bmcweb::AsyncResp>&) { in TEST()
70 [&barCalled](const Request&, const std::shared_ptr<bmcweb::AsyncResp>&, in TEST()
89 std::shared_ptr<bmcweb::AsyncResp> asyncResp = in TEST()
90 std::make_shared<bmcweb::AsyncResp>(); in TEST()
103 const std::shared_ptr<bmcweb::AsyncResp>&) { in __anone77675800502()
119 std::shared_ptr<bmcweb::AsyncResp> asyncResp =
120 std::make_shared<bmcweb::AsyncResp>();
131 [](const Request&, const std::shared_ptr<bmcweb::AsyncResp>&) {}; in __anone77675800602()
[all …]
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/certificate/ |
| H A D | phosphor-certificate-manager_git.bb | 15 PACKAGECONFIG ??= "bmcweb-cert authority-cert"
17 PACKAGECONFIG[bmcweb-cert] = "-Dconfig-bmcweb=enabled,-Dconfig-bmcweb=disabled"
30 …${@bb.utils.contains('PACKAGECONFIG', 'bmcweb', 'phosphor-certificate-manager@bmcweb.service', '',…
|
| /openbmc/phosphor-certificate-manager/ |
| H A D | README.md | 34 --path=/etc/ssl/certs/https/server.pem --unit=bmcweb.service
43 --path=/etc/ssl/certs/authority --unit=bmcweb.service
69 --path=/etc/ssl/certs/https/server.pem --unit=bmcweb.service
75 ## Usage in openbmc/bmcweb
77 OpenBMC [bmcweb](https://github.com/openbmc/bmcweb) exposes various
78 [REST APIs](https://github.com/openbmc/bmcweb/blob/master/redfish-core/lib/certificate_service.hpp)
|
| /openbmc/bmcweb/test/redfish-core/include/ |
| H A D | redfish_oem_routing_test.cpp | 33 const std::shared_ptr<bmcweb::AsyncResp>&, in TEST()
42 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in TEST()
62 std::shared_ptr<bmcweb::AsyncResp> asyncResp = in TEST()
63 std::make_shared<bmcweb::AsyncResp>(); in TEST()
82 [[maybe_unused]] const std::shared_ptr<bmcweb::AsyncResp>& in TEST()
101 [[maybe_unused]] const std::shared_ptr<bmcweb::AsyncResp>& in TEST()
120 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in TEST()
156 std::shared_ptr<bmcweb::AsyncResp> asyncResp = in TEST()
157 std::make_shared<bmcweb::AsyncResp>(); in TEST()
|
| /openbmc/phosphor-webui/ |
| H A D | README.md | 13 bmcweb](https://github.com/openbmc/bmcweb/commit/47c9e106e0057dd70133d50e928e48cbc68e709a)
68 **Note** that some OpenBMC implementations use [bmcweb](https://github.com/openbmc/bmcweb)
69 for its backend. For security reasons, bmcweb will need to be recompiled and
71 option to turn on within bmcweb is `BMCWEB_INSECURE_DISABLE_XSS_PREVENTION`. In
|
| /openbmc/bmcweb/test/redfish-core/include/utils/ |
| H A D | dbus_utils.cpp | 26 std::shared_ptr<bmcweb::AsyncResp> asyncResp = in TEST()
27 std::make_shared<bmcweb::AsyncResp>(); in TEST()
39 std::shared_ptr<bmcweb::AsyncResp> asyncResp = in TEST()
40 std::make_shared<bmcweb::AsyncResp>(); in TEST()
65 std::shared_ptr<bmcweb::AsyncResp> asyncResp = in TEST()
66 std::make_shared<bmcweb::AsyncResp>(); in TEST()
|
| /openbmc/docs/designs/ |
| H A D | certificate-revocation-list.md | 29 2. [BMCWeb](https://github.com/openbmc/bmcweb): the Redfish front-end which
30 translates certificate objects into Redfish resources. BMCWeb is also a
47 3. other daemons, e.g., BMCWeb shall consume CRLs the same way as existing
80 ### BMCWeb subsection
82 We propose to introduce CRLs into BMCWeb's SSL Context. Whenever BMCWeb reloads,
|
| H A D | redfish-authorization.md | 13 enhance the current implementation in BMCWeb Redfish interface so that OpenBMC
80 ### BMCWeb subsection
82 BMCWeb is an OpenBMC Daemon which implements the Redfish service (it implements
85 BMCWeb supports various "authentication" options, but under the hood, to verify
93 After getting the peer's user name, BMCWeb sends DBus queries to
97 | Phosphor-user-manager privileges (implemented as groups) | BMCWeb Redfish Roles |
104 To map Redfish role to their assigned Redfish privileges, BMCWeb implements the
107 | BMCWeb Redfish Roles | Assigned Redfish Privileges …
114 At compile time, BMCWeb assigns each operation of each entity a set of required
115 Redfish Privileges. An authorization action is performed when a BMCWeb route
[all …]
|
| H A D | redfish-spdm-attestation.md | 16 It would be useful to add SPDM attestation support in BMCWeb, which provides
42 - BMCWeb changes for supporting the above Redfish resources.
106 …perimental support for SPDM exists for `bmcweb`](https://github.com/openbmc/bmcweb/compare/master.…
107 which adds routes in the BMCWeb for `ComponentIntegrity` and `TrustedComponent`
108 to support it. But BMCWeb collects the information from D-Bus. The SPDM
185 |BMCWeb+----------->|SPDM | +-------+
251 ### BMCWeb Support
253 In BMCWeb, we need to add routes handler for `ComponentIntegrity`,
277 In BMCWeb, we can reconstruct the following redfish URI by querying the
304 - Extend existing certificate service in BMCWeb.
[all …]
|
| /openbmc/bmcweb/include/ |
| H A D | cookies.hpp | 10 namespace bmcweb namespace
20 "BMCWEB-SESSION=" + session.sessionToken + in setSessionCookies()
27 "BMCWEB-SESSION=" in clearSessionCookies()
32 } // namespace bmcweb
|
| /openbmc/bmcweb/test/include/ |
| H A D | ossl_random.cpp | 14 TEST(Bmcweb, GetRandomUUID) in TEST() argument
16 using bmcweb::getRandomUUID; in TEST()
24 TEST(Bmcweb, GetRandomIdOfLength) in TEST() argument
26 using bmcweb::getRandomIdOfLength; in TEST()
|
| /openbmc/bmcweb/features/ibm/ |
| H A D | ibm_management_console_rest.hpp | 49 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in handleFilePut()
55 if (!bmcweb::asciiIEquals(contentType, "application/octet-stream")) in handleFilePut()
67 "/var/lib/bmcweb/ibm-management-console/configfiles"; in handleFilePut()
77 "/var/lib/bmcweb/ibm-management-console/configfiles"); in handleFilePut()
233 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp) in handleConfigFileList()
237 "/var/lib/bmcweb/ibm-management-console/configfiles"); in handleConfigFileList()
262 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp) in deleteConfigFiles()
266 "/var/lib/bmcweb/ibm-management-console/configfiles"); in deleteConfigFiles()
282 inline void handleFileGet(const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in handleFileGet()
287 "/var/lib/bmcweb/ibm-management-console/configfiles/" + fileID); in handleFileGet()
[all …]
|
| /openbmc/docs/architecture/ |
| H A D | redfish-logging-in-bmcweb.md | 1 # Redfish Event Logging in bmcweb
3 This guide is intended to help developers add new messages to the bmcweb Redfish
6 Redfish Message Objects can be represented in different ways. In bmcweb, we have
18 The bmcweb Message Registries are located under
40 MessageArgs to bmcweb.
46 bmcweb will search the specified Message Registry for the MessageKey, construct
51 The journal is the current mechanism used to log Redfish Messages. bmcweb looks
|
| /openbmc/bmcweb/config/ |
| H A D | meson.build | 98 loglvlopt = get_option('bmcweb-logging')
100 # Override logging level as 'debug' if 'bmcweb-logging' is set as 'disabled'
127 input: 'bmcweb.socket.in',
128 output: 'bmcweb.socket',
159 input: 'bmcweb.socket.in',
175 input: 'bmcweb.service.in',
176 output: 'bmcweb.service',
|
| /openbmc/service-config-manager/ |
| H A D | README.md | 8 An example use case for this service is [BMCWeb's
9 implementation][bmcweb-implementation] of the Redfish NetworkProtocol schema.
13 [bmcweb-implementation]:
14 https://github.com/openbmc/bmcweb/blob/master/redfish-core/lib/network_protocol.hpp
|
| /openbmc/bmcweb/features/google/ |
| H A D | google_service_root.hpp | 37 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp) in handleGoogleV1Get()
51 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp) in handleRootOfTrustCollectionGet()
73 const std::string&, const std::shared_ptr<bmcweb::AsyncResp>&,
78 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in hothGetSubtreeCallback()
110 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in resolveRoT()
128 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in populateRootOfTrustEntity()
152 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in handleRootOfTrustGet()
160 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in invocationCallback()
178 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in invokeRoTCommand()
202 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in handleRoTSendCommandPost()
|
| /openbmc/phosphor-certificate-manager/dist/ |
| H A D | meson.build | 15 if get_option('config-bmcweb').allowed()
16 busconfig += 'busconfig/phosphor-bmcweb-cert-config.conf'
17 certs += 'env/bmcweb'
21 'multi-user.target.wants/phosphor-certificate-manager@bmcweb.service',
|
| /openbmc/bmcweb/redfish-core/lib/ |
| H A D | fan.hpp | 43 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in updateFanList()
68 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in getFanPaths()
98 inline void doFanCollection(const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in doFanCollection()
126 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in handleFanCollectionHead()
152 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in handleFanCollectionGet()
187 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in handleFanPath()
220 const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in getValidFanObject()
248 inline void getFanHealth(const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in getFanHealth()
274 inline void getFanState(const std::shared_ptr<bmcweb::AsyncResp>& asyncResp, in getFanState()
299 inline void getFanLocation(const std::shared_ptr<bmcweb in getFanAsset()
[all...] |