remove meta-tls-common-name-parsing flag
as we remove all `meta-tls-common-name-parsing` usages from all
references in openbmc and bmcweb repos, we can safely remove
`meta-tls-common-name-parsing` flag.
This flag was intended to be a flag to enable meta/facebook specific
auth parse mode. As meta/facebook have migrated our implementation into
using UPN field, we can safely remove all codes related to meta/facebook
specific auth parse mode, including this flag
Tested
- build bmcweb binary
- deploy to a device that already use UPN parse mode
- check if it works fine by sending curl, eg: to /AccountService
Change-Id: Iabffcee177b3c48da90eba97e2a84a8d5a9f57d2
Signed-off-by: Malik Akbar Hashemi Rafsanjani <malikrafsan@meta.com>
diff --git a/config/meson.build b/config/meson.build
index 40bee7f..e62dbec 100644
--- a/config/meson.build
+++ b/config/meson.build
@@ -19,7 +19,6 @@
'insecure-ignore-content-type',
'insecure-push-style-notification',
'kvm',
- 'meta-tls-common-name-parsing',
'mutual-tls-auth',
'redfish',
'redfish-aggregation',
diff --git a/meson.options b/meson.options
index 77aa237..0732e87 100644
--- a/meson.options
+++ b/meson.options
@@ -255,16 +255,6 @@
client's x509 certificate''',
)
-# BMCWEB_META_TLS_COMMON_NAME_PARSING
-option(
- 'meta-tls-common-name-parsing',
- type: 'feature',
- description: '''
- Allows parsing the Subject CN TLS certificate in the format used by
- Meta Inc (see mutual_tls_meta.cpp for details)
- ''',
-)
-
# BMCWEB_IBM_MANAGEMENT_CONSOLE
option(
'ibm-management-console',