tree c36cb54967b8eb11bea140a163e40258364cc905
parent 7fe6d5345a8db26b3382e73ceea44ddad407099d
author Malik Akbar Hashemi Rafsanjani <malikrafsan@meta.com> 1746555812 -0700
committer Ed Tanous <ed@tanous.net> 1746572824 +0000

fix: resolve incorrect key on bmcweb persistent file

This commit is intended to fix the bug on bmcweb when we send patch
request to `/redfish/v1/AccountService`, especially when changing the
`CertificateMappingAttribute`. The expected behavior is that if we
send the patch request, the bmc device will update the internal state
and also update the persistent file (`bmcweb_persistent_data.json`)
to store the current `CertificateMappingAttribute`. This is done so
that after we reboot, the bmc device will retain the
`CertificateMappingAttribute`

However, currently that doesn't happen because there is mismatch on the
key on the persistent file. It should be "MTLSCommonNameParseMode",
instead of "TLSCommonNameParseMode". This commit is intended to solve
this bug

Change-Id: I38f03fd5eefa76079d76552548b411d95639b470
Signed-off-by: Malik Akbar Hashemi Rafsanjani <malikrafsan@meta.com>