commit | 4c549f63e1033b5ee47c54f1a80d060f15133b72 | [log] [tgz] |
---|---|---|
author | Ravi Teja <raviteja28031990@gmail.com> | Tue Nov 26 02:42:27 2024 -0600 |
committer | Ravi Teja <raviteja28031990@gmail.com> | Mon Jan 27 10:10:32 2025 -0600 |
tree | fef9541b43d935427518b515683112da5cb7ef97 | |
parent | 2faed8a3c3d8cb05a026c3bb7516b4824471f338 [diff] |
Add SecretKeyRequired D-bus method This commit adds SecretKeyRequired D-bus method to Manager interface. bmcweb codes needs to query generate secret key required for a given user, local users on BMC have d-bus objects for each user but LDAP users does not have D-bus objects, so this d-bus method helps identify whether generate secret key required for user local and remote LDAP users Change-Id: Ib522802c395d61f0c3e9fbf84fc6a399a66a3afa Signed-off-by: Ravi Teja <raviteja28031990@gmail.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.
This project can be built with meson
. The typical meson
workflow is: meson builddir && ninja -C builddir
.
The meson files used to handle the YAML files are automatically generated and found under the gen
subdirectory. When adding or removing YAML files, this must be regenerated. This can be done with the helper script found in the gen
subdirectory: cd gen && ./regenerate-meson
.
Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true
-Ddata_org_open_power=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir