gbmcweb: enable insecure grpc inband
This is for inband access from other nodes.
Tested: compiles. This option has been running for a long time
on other platforms.
Google-Bug-Id: 303452037
Google-Bug-Id: 315215456
Change-Id: Iccfa0cf34fc2b1b9a034b54e3c7074e8454e0178
Signed-off-by: Nan Zhou <nanzhou@google.com>
(cherry picked from commit d533886cdaa18d1b701abd303101a65591da5c32)
diff --git a/recipes-phosphor/interfaces/bmcweb_%.bbappend b/recipes-phosphor/interfaces/bmcweb_%.bbappend
index c9bfa07..ce01af7 100644
--- a/recipes-phosphor/interfaces/bmcweb_%.bbappend
+++ b/recipes-phosphor/interfaces/bmcweb_%.bbappend
@@ -13,6 +13,7 @@
-Dhealth-populate=disabled \
-Dredfish-bmc-journal=disabled \
"
+
EXTRA_OEMESON:append:gbmc:gbmcfork = " \
-Dgoogle-baremetal=disabled \
"
@@ -156,9 +157,15 @@
}
# gRPC-Redfish feature starts
+# Insecure grpc is needed for the Redfish migration project
+# before nodes get credentials.
+# Note, any insecure port is still blacklist by the nftable.
+# See b/315215456, b/303452037
grpc_redfish_options = " \
-Dmtls-grpc=enabled \
-Dmtls-grpc-port=443 \
+ -Dinsecure-grpc=enabled \
+ -Dinsecure-grpc-port=3995 \
"
grpc_redfish_depends = " \
grpc-redfish \
