diff options
author | Mike Maslenkin <mike.maslenkin@gmail.com> | 2024-08-09 13:16:52 +0300 |
---|---|---|
committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2024-09-05 03:40:45 +0000 |
commit | 7b9f2018d1f2a850eca2ce1431e9eba8f185a716 (patch) | |
tree | d46cb2aafc03905dea49be4af3e36473020efff1 /MdeModulePkg | |
parent | 7acd8c9bd25de8e6af84d1696a8f963eac582089 (diff) | |
download | edk2-7b9f2018d1f2a850eca2ce1431e9eba8f185a716.tar.gz edk2-7b9f2018d1f2a850eca2ce1431e9eba8f185a716.tar.bz2 edk2-7b9f2018d1f2a850eca2ce1431e9eba8f185a716.zip |
RedfishPkg: PlatformHostInterfaceBmcUsbNicLib: use credential protocol
This patch replaces call of IpmiSubmitCommand() issued
REDFISH_IPMI_BOOTSTRAP_CREDENTIAL_ENABLE IPMI command to check
whether bootstrap credential support enabled or not.
The problem is that in accordance with IPMI spec while handling
such command BMC creates bootstrap account. The credentials of this account
is returned as a response. Obviously in this code the response is not used.
From the other side there is an implementation
of EDKII_REDFISH_CREDENTIAL_PROTOCOL exists and used by
RedfishPlatformCredentialIpmiLib.
By design RedfishPlatformCredentialIpmiLib keeps returned bootstrap
credentials and uses it later. So all services using
EDKII_REDFISH_CREDENTIAL_PROTOCOL instance operates with a same
credentials.
Current design of PlatformHostInterfaceBmcUsbNicLib leads to creation
of two bootstrap accounts on BMC side. This is on nesseccary and one
account is not used at all.
Using EDKII_REDFISH_CREDENTIAL_PROTOCOL prevents from creating useless
bootstrap account on BMC side.
Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
Diffstat (limited to 'MdeModulePkg')
0 files changed, 0 insertions, 0 deletions