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>
3 files changed
tree: fef9541b43d935427518b515683112da5cb7ef97
  1. gen/
  2. registry/
  3. subprojects/
  4. yaml/
  5. .gitignore
  6. .markdownlint.yaml
  7. .prettierrc.yaml
  8. .shellcheck
  9. LICENSE
  10. meson.build
  11. meson.options
  12. OWNERS
  13. README.md
  14. requirements.md
README.md

phosphor-dbus-interfaces

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.

Building

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.

Configuration

Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:

  • com/ibm - -Ddata_com_ibm=true
  • org/open_power - -Ddata_org_open_power=true

Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir

References